How to work with multiple namespaces
Like Kubernetes, Epinio has the concept of namespaces, and means of working with them.
Working with multiple of them however is different to Kubernetes.
In Kubernetes the kubectl client accepts an option --namespace for all its commands,
which provide the name of the namespace to work with.
Epinio on the other hand maintains a current namespace in its local state, often also called the targeted namespace.
To work with the applications, configurations, etc. in an existing namespace foo
invoke
epinio target foo
to set foo as the current namespace. All other commands of epinio needing
a namespace will from that point on use foo in their operation.
To start working with a different existing namespace bar simply invoke
epinio target again, i.e. run
epinio target bar
To see the name of the current namespace invoke the command without a namespace argument, i.e.:
epinio target
The current namespace is local state, specific to the user invoking the Epinio client. The information is not shared between users.
Creating a new namespace does not make it the current namespace.
Deleting the current namespace does not undo the targeting. The removed namespace stays targeted.
However all commands using a namespace will report it as not existing and fail to work.
While installation of Epinio creates a pre-defined namespace workspace the helm chart
is not able to automatically target this namespace. This has to be done by the user.
This, and the previous caution also means that whatever namespace was targeted last in a preceding installation of Epinio will still be targeted in a new installation.