Skip to main content
Version: Next 🚧

Working with namespaces

This guide explores working with namespaces. It assumes that Epinio is installed; if you need to install, see install Epinio.

Like Kubernetes, Epinio has an idea of namespaces, and the means of working with them. Working with many namespaces is a little different in Epinio than with Kubernetes.

In Kubernetes the kubectl client accepts an option --namespace for all its commands, naming the namespace to work with. Epinio instead maintains a current namespace in its local state, often also called the targeted namespace. Commands that operate on a namespace use the current one.

There are a few points to note:

  • The current namespace is local state, specific to the user invoking the Epinio client. The state information isn't shared between users.
  • Creating a new namespace doesn't make it the current namespace.
  • Deleting the current namespace doesn't undo the targeting. The removed namespace stays targeted and so the next commands fail.
  • While installation of Epinio creates the pre-defined namespace workspace, the Helm chart is not able to automatically target this namespace. The user must do this. This means whatever namespace was the last target in a preceding installation of Epinio continues to be the target in a new installation.

Working with namespaces

UI walkthrough coming soon.

See also