Kubernetes Architecture, Operations, and Troubleshooting Questions

How Kubernetes works, how to run it, and how to debug it. Covers control-plane and node components, the scheduler and API server, cluster design, high availability and multi-cluster topologies, and platform-level operations; the workload primitives (pods, deployments, services, controllers), cluster upgrades, and designing Kubernetes as an internal platform; and the operational depth inside a cluster including pod and service networking, ingress and the CNI model, service mesh, persistent volumes and storage classes, resource requests and limits, and systematically diagnosing scheduling, networking, and storage failures. The full architecture-through-day-two-operations span of Kubernetes.

MediumTechnical
84 practiced

You are troubleshooting PersistentVolumeClaim (PVC) not binding to any PersistentVolume (PV). Describe the steps to debug PV/PVC binding: inspect storage class, volumeMode, accessModes, reclaimPolicy, CSI provisioner logs, and cloud provider storage quotas. Provide kubectl commands and sample outputs you would expect in common failure cases.

EasyTechnical
44 practiced

Describe the kubectl commands and rollout strategies you would use to perform a safe rolling restart of a Deployment, view rollout history, and rollback to a previous revision. Include examples using kubectl and explain how you would avoid causing cascading failures during a restart of a consumer‑facing service.

HardTechnical
39 practiced

Explain Kubernetes networking end-to-end: pod IP model, service virtual IPs, kube-proxy modes (iptables vs IPVS), CNI plugins and how they implement pod networking, and practical debugging steps when pods on different nodes cannot reach each other on specific TCP ports. Include commands and sources of truth to inspect.

MediumTechnical
50 practiced

Explain the differences between Deployment and StatefulSet. Provide a scenario (e.g., a database cluster) that requires StatefulSet semantics and explain which StatefulSet features (stable network IDs, ordinal indexes, persistent volumes) are necessary.

MediumTechnical
73 practiced

Explain Kubernetes resource requests, limits, and QoS classes (Guaranteed, Burstable, BestEffort). How do these settings affect scheduler decisions, eviction behavior under memory pressure, and node overcommit? Provide practical guidance for right-sizing microservice resource requests and limits.

Unlock Full Question Bank

Get access to all Kubernetes Architecture, Operations, and Troubleshooting interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.