Skip to content

Instantly share code, notes, and snippets.

@jzaccone
Last active September 6, 2017 14:51
Show Gist options
  • Save jzaccone/f01d435f343937dd3c74466c312195f3 to your computer and use it in GitHub Desktop.
Save jzaccone/f01d435f343937dd3c74466c312195f3 to your computer and use it in GitHub Desktop.
kubectl create namespace <new namespace>
kubectl config set-context $(kubectl config current-context) --namespace=<insert-namespace-name-here>
kubectl config view | grep namespace:
#Namespaces are intended for use in environments with many users spread across multiple teams, or projects. For clusters with a few to tens of users, you should not need to create or think about namespaces at all. Start using namespaces when you need the features they provide.
#Namespaces provide a scope for names. Names of resources need to be unique within a namespace, but not across namespaces.
#Namespaces are a way to divide cluster resources between multiple uses (via resource quota).
#In future versions of Kubernetes, objects in the same namespace will have the same access control policies by default.
#It is not necessary to use multiple namespaces just to separate slightly different resources, such as different versions of the same software: use labels to distinguish resources within the same namespace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment