KCNA · Question #189
What are the initial namespaces that Kubernetes starts with?
The correct answer is A. default, kube-system, kube-public, kube-node-lease. Kubernetes automatically creates several default namespaces upon cluster initialization, including default for general use, kube-system for system-critical objects, kube-public for publicly readable resources, and kube-node-lease for node heartbeats.
Question
What are the initial namespaces that Kubernetes starts with?
Options
- Adefault, kube-system, kube-public, kube-node-lease
- Bdefault, system, kube-public
- Ckube-default, kube-system, kube-main, kube-node-lease
- Dkube-default, system, kube-main, kube-primary
How the community answered
(26 responses)- A88% (23)
- C8% (2)
- D4% (1)
Why each option
Kubernetes automatically creates several default namespaces upon cluster initialization, including `default` for general use, `kube-system` for system-critical objects, `kube-public` for publicly readable resources, and `kube-node-lease` for node heartbeats.
When a Kubernetes cluster is initialized, it automatically creates four default namespaces: `default` for objects without a specific namespace, `kube-system` for components managed by Kubernetes itself, `kube-public` for resources accessible by all users, and `kube-node-lease` which holds Lease objects for node heartbeats to improve scalability of node status updates.
While `default` and `kube-public` are correct, `system` is not a standard initial namespace; it's `kube-system`.
`kube-default` and `kube-main` are not standard initial namespaces created by Kubernetes.
`kube-default`, `system`, `kube-main`, and `kube-primary` are all incorrect names for the standard initial namespaces.
Concept tested: Kubernetes default namespaces
Source: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#initial-namespaces
Topics
Community Discussion
No community discussion yet for this question.