The Kubernetes Namespaces You Should Never Touchby@amrhassan
1,176 reads

The Kubernetes Namespaces You Should Never Touch

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

Kubernetes is shipped with many namespaces. Namespaces will be regenerated again even when you delete them accidentally. This is useful for exposing any cluster information necessary to bootstrap components. Namespace is mostly reserved for public use, in case some resources should be visible and readable publicly throughout the whole cluster. It is primarily managed by KuberNETes itself. It will be used to handle external/internal communications and security issues with controllers and deploying new pods/deployment. The above is the default place of objects you create with no namespace specified.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - The Kubernetes Namespaces You Should Never Touch
Amr Hassan HackerNoon profile picture


Amr Hassan

Unlocking the secrets of efficient code with 6+ yrs exp. Join me on a journey to becoming a better engineer

Receive Stories from @amrhassan

react to story with heart


. . . comments & more!