Bird
0
0

Why does kubectl get all not always list every resource in the cluster?

hard📝 Conceptual Q10 of 15
Kubernetes - kubectl Essential Commands
Why does kubectl get all not always list every resource in the cluster?
ABecause 'all' requires --all-namespaces flag to work
BBecause 'all' lists resources only in the default namespace
CBecause 'all' is deprecated and no longer supported
DBecause 'all' only includes common resource types, not custom or less common ones
Step-by-Step Solution
Solution:
  1. Step 1: Understand what 'all' includes

    kubectl get all lists common resource types like pods, services, deployments.
  2. Step 2: Recognize it excludes custom or rare resources

    Custom resources or some resource types are not included in 'all'.
  3. Final Answer:

    Because 'all' only includes common resource types, not custom or less common ones -> Option D
  4. Quick Check:

    'all' = common resources only [OK]
Quick Trick: 'kubectl get all' excludes custom resources [OK]
Common Mistakes:
  • Thinking 'all' lists every resource including custom ones
  • Assuming it needs --all-namespaces to list all resources

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes