You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/installation/installation.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,7 @@ The script will create two different types of Kubernetes clusters, each consisti
100
100
```
101
101
102
102
5. At the beginning of the script execution, a check is performed to ensure all [required tools](#prerequisites) are installed. If any dependencies are missing, the script will prompt you for confirmation before proceeding with their automatic installation.
103
+
>**Note** The tools will be installed assuming Linux as the operating system. If you are not using Linux, you will need to install them manually.
103
104
104
105
If Docker is not installed and you choose to install it, the script will terminate after its installation. This is necessary because the Docker group must be reloaded in order to use Docker commands without sudo. You can achieve this by running:
105
106
@@ -109,7 +110,7 @@ The script will create two different types of Kubernetes clusters, each consisti
109
110
110
111
This command opens a new shell with updated group permissions. After executing it, simply restart the installation script.
111
112
112
-
6. After executing the script, you can verify the status of the pods in the consumer cluster using the following commands:
113
+
1. After executing the script, you can verify the status of the pods in the consumer cluster using the following commands:
113
114
114
115
```sh
115
116
export KUBECONFIG=fluidos-consumer-1-config
@@ -131,7 +132,7 @@ The script will create two different types of Kubernetes clusters, each consisti
131
132
132
133
This approach enables seamless monitoring of both consumer and provider clusters without needing to re-export environment variables manually.
133
134
134
-
7. You should see 4 pods running on the `fluidos-consumer` cluster and 4 pods running on the `fluidos-provider` cluster:
135
+
2. You should see 4 pods running on the `fluidos-consumer` cluster and 4 pods running on the `fluidos-provider` cluster:
0 commit comments