Default namespaces overview in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

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

In Kubernetes, several default namespaces exist. What is the main role of the kube-system namespace?

A It contains system components and services managed by Kubernetes itself.

B It is used for user-created applications and workloads.

C It stores temporary data and logs for debugging purposes.

D It is reserved for network policies and ingress controllers only.

💡 Hint

Think about where Kubernetes keeps its own essential services.

The kube-system namespace holds the core Kubernetes components like the scheduler, controller manager, and DNS services. It is not meant for user workloads.

💻 Command Output

intermediate

Output of listing namespaces in a fresh Kubernetes cluster

What is the output of the command kubectl get namespaces immediately after installing a new Kubernetes cluster?

Kubernetes

kubectl get namespaces

A

NAME          STATUS   AGE
default       Active   1m
kube-system   Active   1m
kube-public   Active   1m

B

NAME          STATUS   AGE
default       Active   1m
user-space    Active   1m
kube-system   Active   1m

C

NAME          STATUS   AGE
default       Active   1m
kube-system   Active   1m
kube-public   Active   1m
kube-node-lease Active   1m

D

NAME          STATUS   AGE
default       Active   1m
kube-public   Active   1m
kube-node-lease Active   1m

💡 Hint

Remember the default namespaces Kubernetes creates for system and node management.

A fresh Kubernetes cluster typically has four default namespaces: default, kube-system, kube-public, and kube-node-lease.

❓ Configuration

advanced

Effect of creating a pod without specifying a namespace

If you create a pod using kubectl apply -f pod.yaml and the pod manifest does not specify a namespace, where will the pod be created?

A In a new namespace named after the pod.

B In the <code>default</code> namespace.

C In the <code>kube-system</code> namespace.

D The command will fail due to missing namespace.

💡 Hint

Think about Kubernetes' default behavior when no namespace is given.

When no namespace is specified, Kubernetes places resources in the default namespace automatically.

❓ Troubleshoot

advanced

Why can't a pod in 'default' namespace access a service in 'kube-system' namespace without specifying namespace?

You have a pod in the default namespace trying to access a service named dns-service in the kube-system namespace using just dns-service as the hostname. Why does this fail?

A Because the service <code>dns-service</code> does not exist in <code>kube-system</code>.

B Because services in <code>kube-system</code> are blocked by default network policies.

C Because pods in <code>default</code> cannot communicate with pods in <code>kube-system</code> at all.

D Because DNS resolution in Kubernetes requires the full service name including namespace for cross-namespace access.

💡 Hint

Think about how Kubernetes DNS resolves service names across namespaces.

To access a service in another namespace, you must use the full DNS name: service-name.namespace.svc.cluster.local. Using just the service name only works within the same namespace.

✅ Best Practice

expert

Recommended namespace usage for multi-team Kubernetes cluster

You manage a Kubernetes cluster shared by multiple teams. What is the best practice regarding namespaces to isolate team workloads?

A Create a separate namespace for each team to isolate resources and apply team-specific policies.

B Use the <code>default</code> namespace for all teams to simplify management.

C Create namespaces only for system components and put all teams in one namespace.

D Avoid namespaces and use labels on pods to separate teams.

💡 Hint

Think about how namespaces help with resource isolation and access control.

Namespaces provide a natural boundary for resource isolation, quota management, and access control, making them ideal for separating teams in a shared cluster.