3.0. Namespaces

Last updated 16 days ago

Now that you have a working cluster connected to your Kubernetic client you can continue with handling the namespaces.

Note: make sure your cluster where you run the tutorial is not your production environment. Although we take precautions to avoid mingling with existing cluster load, there are no guaranties of no interference.

Namespaces is a way to virtually split an existing cluster to separate environments. Most objects inside Kubernetes act inside a specific namespace, which means when you switch namespace a fresh environment will be provided.

Go to the Settings > Namespaces screen.

You will see there your existing namespaces. Kubernetes creates an active "default" namespace automatically which is where your objects act on by default. It also creates a "kube-system" namespace where all cluster's management objects are stored (e.g. A DNS service).

Let's create a namespace:

  • Fill name: kubernetic-tutorial

  • Click Add Namespace button

You will automatically be directed to the newly created namespace. You can see your active namespace a the top menu bar.

Also, your kubectl configuration has been updated and the current context now points to the new namespace. So if you use kubectl now it will be in sync with the cluster and namespace you view in Kubernetic. If you switch using kubectl the context, Kubernetic will pick up the change and show you the selected context.