Clarify that spawning network in k8s should be in default namespace

README.md

@@ -178,6 +178,18 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 Note that the command expects two binaries `polkadot` and `adder-collator` to be installed on your system. See further down for how to get them.
 
 You can follow the output of the `steps` to spawn the network and once the network is launched a

docs/src/cli/spawn.md

@@ -33,6 +33,18 @@ Then you can spawn the network by running the following command:
 ./zombienet-macos spawn examples/0001-small-network.toml
 ```
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 You can follow the output of the `steps` to spawn the network and once the network is launched a message with the `node`s information like this one is show
 
 ```bash

docs/src/cli/testing.md

@@ -5,6 +5,18 @@ Those assertions should be defined in a _feature test_, and the `dsl` and format
 
 The following is a small example to spawn a network (using the previous `simple network definition`) and assert that:
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 - Both `nodes` are running
 - The defined `parachain` is registered
 - The defined `parachain` is producing blocks and produced at least 10 within 200 seconds.

docs/src/guide.md

@@ -6,6 +6,18 @@ Zombienet was designed to be a flexible and easy to use tool, allowing users to
 
 In this guide we will go through simple use cases as well as more complex ones, describing the trade-offs made and the _current_ constraints for both network configurations and test specifications.
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 ---
 
 ### Example 0 - Different configuration file types (2 validators)

javascript/README.md

@@ -177,6 +177,18 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 Note that the command expects two binaries `polkadot` and `adder-collator` to be installed on your system. See further down for how to get them.
 
 You can follow the output of the `steps` to spawn the network and once the network is launched a

javascript/packages/cli/README.md

@@ -177,6 +177,18 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 Note that the command expects two binaries `polkadot` and `adder-collator` to be installed on your system. See further down for how to get them.
 
 You can follow the output of the `steps` to spawn the network and once the network is launched a

javascript/packages/orchestrator/README.md

@@ -177,6 +177,18 @@ Then you can spawn the network by running the following command:
 ❯ ./zombienet-macos spawn --provider native examples/0001-small-network.toml
 ```
 
+**Note:** before spawning network one needs to verify that `kubectl`'s namespace is set to `default`
+```bash
+❯ kubectl config get-contexts
+
+CURRENT   NAME                   CLUSTER          AUTHINFO         NAMESPACE
+*         docker-desktop         docker-desktop   docker-desktop   default
+
+# if not then set it to default value
+
+❯ kubectl config set-context --current --namespace='default'
+```
+
 Note that the command expects two binaries `polkadot` and `adder-collator` to be installed on your system. See further down for how to get them.
 
 You can follow the output of the `steps` to spawn the network and once the network is launched a

javascript/words.txt

@@ -6,6 +6,7 @@ anguage
 asgn
 astar
 auths
+AUTHINFO
 autoremove
 availables
 aventus