Bird
0
0

A user runs kubectl get pods without specifying a namespace and sees no pods. What is the most probable reason?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Namespaces
A user runs kubectl get pods without specifying a namespace and sees no pods. What is the most probable reason?
AThe user is not authenticated
Bkubectl command is missing the --all-namespaces flag
CThe kube-system namespace is empty
DNo pods exist in the default namespace
Step-by-Step Solution
Solution:

  1. Step 1: Understand default namespace behavior

    When no namespace is specified, kubectl uses the default namespace.

  2. Step 2: Reason about empty pod list

    If no pods appear, it means the default namespace has no pods currently.

  3. Final Answer:

    No pods exist in the default namespace -> Option D

  4. Quick Check:

    kubectl default namespace = no pods found [OK]
Quick Trick: kubectl defaults to default namespace if none given [OK]
Common Mistakes:
  • Assuming kube-system is empty
  • Thinking --all-namespaces is required to see default pods
  • Assuming authentication error without evidence

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Node components (kubelet, kube-proxy, container runtime) - Quiz 4medium Namespaces - Cross-namespace communication - Quiz 3easy Pods - Sidecar container pattern - Quiz 15hard Pods - Why Pods are the smallest deployable unit - Quiz 5medium ReplicaSets and Deployments - Deployment as higher-level abstraction - Quiz 11easy ReplicaSets and Deployments - Deployment as higher-level abstraction - Quiz 7medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 11easy Services - Endpoints and endpoint slices - Quiz 5medium Services - NodePort service type - Quiz 5medium kubectl Essential Commands - kubectl get for listing resources - Quiz 10hard