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.

Practice

1. What is the purpose of namespaces in Kubernetes?

easy

A. To replace pods in the cluster

B. To increase the CPU speed of nodes

C. To organize resources into separate groups within a cluster

D. To store container images

Solution

1. Step 1: Understand what namespaces do

   Namespaces help group and isolate resources in a Kubernetes cluster.

2. Step 2: Identify the correct purpose

   They do not affect CPU speed, store images, or replace pods.

3. Final Answer:

   To organize resources into separate groups within a cluster -> Option C

4. Quick Check:

   Namespaces organize resources [OK]

Hint: Namespaces group resources logically in Kubernetes [OK]

Common Mistakes:

• Thinking namespaces speed up nodes
• Confusing namespaces with image storage
• Believing namespaces replace pods

2. Which of the following is a default namespace in Kubernetes?

easy

A. user-space

B. production

C. development

D. kube-system

Solution

1. Step 1: Recall default namespaces

   Kubernetes provides default namespaces like default, kube-system, and kube-public.

2. Step 2: Identify the correct default namespace

   kube-system is a default namespace for system components, while others are user-defined.

3. Final Answer:

   kube-system -> Option D

4. Quick Check:

   kube-system is default namespace [OK]

Hint: Remember kube-system for system pods [OK]

Common Mistakes:

• Assuming production is default
• Confusing user namespaces with defaults
• Thinking development is built-in

3. What will the command kubectl get pods -n default show?

medium

A. Pods in the default namespace

B. All pods in all namespaces

C. Pods in the kube-system namespace

D. No pods, because default namespace is empty

Solution

1. Step 1: Understand the command syntax

   kubectl get pods -n default lists pods in the namespace named default.

2. Step 2: Identify the namespace targeted

   The -n default flag limits output to the default namespace only.

3. Final Answer:

   Pods in the default namespace -> Option A

4. Quick Check:

   kubectl -n default shows default pods [OK]

Hint: -n specifies namespace for kubectl commands [OK]

Common Mistakes:

• Thinking it shows pods from all namespaces
• Confusing default with kube-system
• Assuming default namespace is always empty

4. You run kubectl get pods but get an error: error: namespace "defaultt" not found. What is the likely cause?

medium

A. Pods do not exist in any namespace

B. The namespace name is misspelled

C. kubectl is not installed

D. The cluster is down

Solution

1. Step 1: Analyze the error message

   The error says namespace "defaultt" not found, indicating a typo.

2. Step 2: Check command usage

   Likely the user typed defaultt instead of default as namespace.

3. Final Answer:

   The namespace name is misspelled -> Option B

4. Quick Check:

   Namespace typo causes not found error [OK]

Hint: Check spelling of namespace names carefully [OK]

Common Mistakes:

• Assuming pods don't exist anywhere
• Blaming kubectl installation
• Thinking cluster is down without checking

5. You want to deploy an app only visible to system components. Which default namespace should you use?

hard

A. kube-system

B. kube-public

C. default

D. custom-namespace

Solution

1. Step 1: Understand namespace roles

   kube-system holds system components and is isolated from normal user apps.

2. Step 2: Choose namespace for system visibility

   Deploying in kube-system makes the app visible only to system components.

3. Final Answer:

   kube-system -> Option A

4. Quick Check:

   System apps use kube-system namespace [OK]

Hint: Use kube-system for system-only apps [OK]

Common Mistakes:

• Using default namespace for system apps
• Choosing kube-public which is for public info
• Using a custom namespace without system access