![]() There is absolutely nothing special about this Namespace, except that the Kubernetes tooling is set up out of the box to use this namespace and you can’t delete it. kube-public isn’t really used for much right now, and it’s usually a good idea to leave kube-system alone, especially in a managed system like Google Kubernetes Engine (GKE). This leaves the default Namespace as the place where your services and apps are created. In most Kubernetes distributions, the cluster comes out of the box with a Namespace called “default.” In fact, there are actually three namespaces that Kubernetes ships with: default, kube-system (used for Kubernetes components), and kube-public (used for public resources). They can help you and your teams with organization, security, and even performance! You can have multiple namespaces inside a single Kubernetes cluster, and they are all logically isolated from each other. You can think of a Namespace as a virtual cluster inside your Kubernetes cluster.
0 Comments
Leave a Reply. |