Skip to content

Commit ff663dd

Browse files
committed
Fix: Added note for installing tool with different OS
1 parent 2276544 commit ff663dd

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/installation/installation.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,7 @@ The script will create two different types of Kubernetes clusters, each consisti
100100
```
101101

102102
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.
103104

104105
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:
105106

@@ -109,7 +110,7 @@ The script will create two different types of Kubernetes clusters, each consisti
109110

110111
This command opens a new shell with updated group permissions. After executing it, simply restart the installation script.
111112

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:
113114

114115
```sh
115116
export KUBECONFIG=fluidos-consumer-1-config
@@ -131,7 +132,7 @@ The script will create two different types of Kubernetes clusters, each consisti
131132

132133
This approach enables seamless monitoring of both consumer and provider clusters without needing to re-export environment variables manually.
133134

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:
135136

136137
- `node-local-resource-manager-<random>`
137138
- `node-network-manager-<random>`

0 commit comments

Comments
 (0)