Skip to content

Commit f71e844

Browse files
authored
adding common KIND issues in testbed information (#45)
It introduces some side notes on the test-bed installation setup concerning possible issue when running multi-cluster environments in KIND.
1 parent b7adbc1 commit f71e844

1 file changed

Lines changed: 14 additions & 1 deletion

File tree

testbed/kind/README.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,19 @@ This guide will create two different Kubernetes clusters:
2727
- [Helm](https://helm.sh/docs/intro/install/)
2828
- [Liqo CLI tool](https://docs.liqo.io/en/v0.10.1/installation/liqoctl.html)
2929

30-
### Installation
30+
## Common issues with KIND
31+
32+
This setup relies on KIND (Kubernetes in Docker) to quickly establish a reliable testbed for testing the FLUIDOS Node architecture.
33+
34+
There are common issues encountered when running multiple clusters with KIND, particularly related to swap space memory usage and resource limits within the operating systems.
35+
36+
Therefore, we highly recommend running the following commands before proceeding with the installation process:
37+
38+
1. `sudo swapoff -a`
39+
2. `sudo sysctl fs.inotify.max_user_instances=512`
40+
3. `sudo sysctl fs.inotify.max_user_watches=524288`
41+
42+
## Installation
3143

3244
1. Clone the repository
3345

@@ -155,6 +167,7 @@ You can now create a demo namespace on the `fluidos-consumer` cluster:
155167
```sh
156168
kubectl create namespace demo
157169
```
170+
158171
And then offload the namespace to the `fluidos-provider` cluster:
159172

160173
```sh

0 commit comments

Comments
 (0)