What is the purpose of the 'kube-system' namespace in Kubernetes?

What is the purpose of the 'kube-system' namespace in Kubernetes?

• A. It is for objects created by the Kubernetes system
• B. It is for user secrets
• C. It stores application logs only
• D. It contains all network policies

Answer: (D)

The kube-system namespace is where Kubernetes runs its own system components. It isolates the control plane processes and cluster add-ons (like the API server, etcd, scheduler, controller-manager, and components such as CoreDNS or kube-proxy) from regular user workloads. This separation helps with security, RBAC, and resource management, so system components aren’t mixed with application workloads. Secrets aren’t restricted to kube-system; they’re namespace-scoped resources and can reside in the namespace where your application runs (or wherever you choose). Logs aren’t stored in a special namespace by design; you access pod logs via kubectl or a logging stack. Network policies aren’t confined to kube-system either; they’re defined per namespace to control traffic within and between namespaces.

The kube-system namespace is where Kubernetes runs its own system components. It isolates the control plane processes and cluster add-ons (like the API server, etcd, scheduler, controller-manager, and components such as CoreDNS or kube-proxy) from regular user workloads. This separation helps with security, RBAC, and resource management, so system components aren’t mixed with application workloads.

Secrets aren’t restricted to kube-system; they’re namespace-scoped resources and can reside in the namespace where your application runs (or wherever you choose). Logs aren’t stored in a special namespace by design; you access pod logs via kubectl or a logging stack. Network policies aren’t confined to kube-system either; they’re defined per namespace to control traffic within and between namespaces.