solving lintint

deployments/node/README.md

@@ -38,7 +38,6 @@ A Helm chart for Fluidos Node
 | networkManager.pod.labels | object | `{}` | Labels for the network-manager pod. |
 | networkManager.pod.resources | object | `{"limits":{},"requests":{}}` | Resource requests and limits (https://kubernetes.io/docs/user-guide/compute-resources/) for the network-manager pod. |
 | networkManager.replicas | int | `1` | The number of Network Manager, which can be increased for active/passive high availability. |
-| provider | string | `"your-provider"` |  |
 | pullPolicy | string | `"IfNotPresent"` | The pullPolicy for fluidos-node pods. |
 | rearController.imageName | string | `"ghcr.io/fluidos-project/rear-controller"` |  |
 | rearController.pod.annotations | object | `{}` | Annotations for the rear-controller pod. |

docs/installation/installation.md

@@ -35,6 +35,7 @@ No options are available through the CLI, but you can choose the installation mo
 The option supported are:
 
 - `1` to install the FLUIDOS Node as the demo testbed through KIND
+
 - `2` to install the FLUIDOS Node in n consumer clusters and m provider clusters through KIND
 <!-- - `3` to install the FLUIDOS Node in n clusters through their KUBECONFIG files
   **DISCLAIMER:** in this case all your Kubernetes clusters inserted in the script must have at least one node tagged with `node-role.fluidos.eu/worker: "true"` and at least in the provider clusters, you can choose the nodes that exposes their Kubernetes resources with the label `node-role.fluidos.eu/resources: "true"`. -->
@@ -52,7 +53,6 @@ cd ../../tools/scripts
 
 This script will delete both the kind clusters and their corresponding kubeconfig files.
 
-
 ## Manual installation
 
 Please, make sure you have [helm](https://helm.sh/docs/intro/install/) installed.