solving linting issues

fluidos-project · Jul 12, 2024 · 3a6e13d · 3a6e13d
1 parent c913c18
commit 3a6e13d
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/docs/installation/installation.md b/docs/installation/installation.md
@@ -3,7 +3,9 @@
 This section shows the installation process of the FLUIDOS Node components.
 
 There are two ways to install FLUIDOS Node components:
+
 1. Launching the testbed environment with a script.
+
 2. Installing the FLUIDOS Node manually on your Kubernetes cluster.
 
 If it's your first time with FLUIDOS Node components, we suggest the testbed environment via script. This allows you to install as many kind clusters as you want to run your experiments.
@@ -67,9 +69,10 @@ To ensure you have Liqo, please run the following script:
 cd ../../tools/scripts
 ./install-liqo.sh <provider> <cluster-name> $KUBECONFIG
 ```
+
 Please, note that you need to pass a few parameters.
 
--  "provider": this parameter depends on your Kubernetes installation.
+- "provider": this parameter depends on your Kubernetes installation.
     We currently test it on the following providers:
       1. kubeadm
       2. k3s
@@ -78,16 +81,12 @@ Please, note that you need to pass a few parameters.
 
 - $KUBECONFIG: it is the typical environment variable that points to the path of your Kubernetes cluster configuration.
 
-
-
-
 For more information, check out [Liqo official documentation](https://docs.liqo.io/en/v0.10.3/installation/install.html#install-with-liqoctl) for all supported providers.
 
-**DISCLAIMER:** before going ahead, ensure that at least one node is tagged with `node-role.fluidos.eu/worker: "true"` and, if acting as a provider, choose the nodes that exposes their Kubernetes resources with the label `node-role.fluidos.eu/resources: "true"`. 
+**DISCLAIMER:** before going ahead, ensure that at least one node is tagged with `node-role.fluidos.eu/worker: "true"` and, if acting as a provider, choose the nodes that exposes their Kubernetes resources with the label `node-role.fluidos.eu/resources: "true"`.
 
 Once we have Liqo running, we can install the FLUIDOS Node component via helm:
 
-
 ```bash
 helm repo add fluidos https://fluidos-project.github.io/node/
 
@@ -102,6 +101,7 @@ helm install node fluidos/node -n fluidos \
 Due to the absence of the Network Manager component that enable the auto-discovery among FLUIDOS Nodes, we need to setup some parameters manually to allow Nodes discovery.
 
 Here, the meaning of the various parameters:
+
 - LOCAL_K8S_CLUSTER_CP_IP: The IP address of your local Kubernetes cluster Control Plane
 - LOCAL_REAR_PORT: The port on which your local cluster uses the REAR protocol
 - REMOTE_K8S_CLUSTER_CP_IP: It's the IP address of the remote Kubernetes cluster to which you want to negotiate Flavors thorugh REAR with.

diff --git a/tools/scripts/install_liqo.sh b/tools/scripts/install_liqo.sh
@@ -32,7 +32,7 @@ CLUSTER_NAME=$2
 KUBECONFIG_LIQO=$3
 
 # Install Liqo based on the provider
-liqoctl install "$PROVIDER" --cluster-name "$cluster_name" --kubeconfig "$KUBECONFIG_LIQO" || { echo "Failed to install Liqo for provider: $PROVIDER"; exit 1; }
+liqoctl install "$PROVIDER" --cluster-name "$CLUSTER_NAME" --kubeconfig "$KUBECONFIG_LIQO" || { echo "Failed to install Liqo for provider: $PROVIDER"; exit 1; }
 # liqoctl install "$PROVIDER" || { echo "Failed to install Liqo for provider: $PROVIDER"; exit 1; }
 
 echo "Liqo installation for provider $PROVIDER completed successfully."