Enterprise Kubernetes, delivered

Tectonic ships with CoreOS's signature automated operations, runs multi-cloud, and is the fastest, most secure path to Kubernetes.

Managing Namespaces in Tectonic

Namespaces are one way that Kubernetes scopes and restricts resource usage within a single cluster.

For those looking to administrate users on a Tectonic Kubernetes cluster, read the User Management guide which covers Kubernetes Role Based Access Controls.

Create a namespace with kubectl

To create a Kubernetes namespace, create a yaml resource file staging.yaml with the following contents:

apiVersion: v1
kind: Namespace
  name: staging

The Namepsace can be created, used, and deleted with the following commands:

$ kubectl create -f staging.yaml
namespace "staging" created
$ kubectl get namespace staging
staging   Active    1m
$ kubectl run nginx --image=nginx --namespace=staging
deployment "nginx" created
$ kubectl describe namespace staging
Name:   staging
Labels: <none>
Status: Active

No resource quota.

No resource limits.
$ kubectl get deployments --namespace=staging
nginx     1         1         1            1           3m
$ kubectl delete namespace staging  # This deletes all resources under the `staging` namespace!
namespace "staging" deleted

Monitor namespaces with Tectonic Console

Once a Namespace is set on a cluster, that namepsace's can be monitored by toggling the "Namespace" dropdown at the top of the page. A list of Namespaces can be viewed in the Admin section of the Console.

Default namespaces

Check out the Kubernetes Namespace User Guide for more information about Kubernetes Namespaces.