Interview Kubernetes, Docker, Helm & Podman

What does kubectl describe show that kubectl get does not?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

kubectl get gives a compact current view. kubectl describe adds details such as events, conditions, selected node, image IDs, mounts, resource settings, probe status, and reasons behind scheduling or runtime failures.

Technical explanation

describe is especially useful because it includes chronological Events that kubectl get does not show by default.

For deeper inspection, pair describe with kubectl get -o yaml to see exact spec and status fields.

Troubleshooting starts from state and events: get, describe, logs, previous logs, events, and then node/runtime/network checks.

Separate scheduling failures, image pull failures, runtime failures, app failures, and traffic-routing failures so you do not fix the wrong layer.

Operational commands like drain and rollback must respect PDBs, probes, and workload disruption tolerance.

Hands-on example

1. In a non-production namespace, create this safe broken scenario: compare kubectl get, describe, and get -o yaml for the same Pod.

2. Follow a fixed triage order: kubectl get, describe, logs or logs --previous, events, rollout status, node status, and then runtime/network checks.

3. Fix only one variable at a time so the root cause is clear rather than accidentally masked.

4. Save the commands and final diagnosis as an interview-ready incident walkthrough.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions