Kubernetes interview question · Most asked
How would you design a production-ready Kubernetes platform for several teams?
Summary
Start from the developer experience and guardrails: standard templates (golden paths) for services, GitOps deployment, built-in observability, secrets integration, policy enforcement, autoscaling, and clear ownership. Underneath: managed clusters per environment (and sometimes per region), infrastructure as code, a tested upgrade process and cost visibility.
Longer Answer
Components typically include: a managed control plane; node provisioning with autoscaling; a CNI with NetworkPolicy; ingress or Gateway API with cert-manager; External Secrets; Prometheus/Grafana/OpenTelemetry; Argo CD or Flux; Kyverno or Gatekeeper; backup with Velero; and an internal developer portal (Backstage) with templates. Define SLOs for the platform itself, document the paved road, and treat the platform as a product with users.
Key Points
- Golden paths and guardrails.
- Managed clusters, IaC, regular upgrades.
- GitOps, observability, policy, secrets built in.
- Platform as a product with SLOs.
Explanation
What interviewers look for
Thinking about users (developers), guardrails and operations, not just a list of tools.
More most-asked Kubernetes questions
- ConfigMaps and Secrets: how do they differ, and how should secrets really be handled?
- How does the scheduler place pods? Explain resource requests, node affinity, taints and tolerations.
- Describe the Kubernetes architecture: what runs on the control plane and what runs on the nodes?
- How do rolling updates work in a Deployment, and how do you roll back?
- Explain the Service types: ClusterIP, NodePort, LoadBalancer, ExternalName and headless.
- What happens, step by step, when you run kubectl apply for a Deployment?
- Deployment, StatefulSet, DaemonSet, Job and CronJob: when do you use each?
- What is the difference between resource requests and limits, and what are the QoS classes?