DevOpsInterview.Cloud
Cover of Containers & Orchestration: Kubernetes Interview Questions
Book 2

Containers & Orchestration: Kubernetes Interview Questions

52 questions · 8 chapters · 194 pages · 2026 edition

  • This bookPDF, 194 pages, emailed after payment

    ₹899
    Buy this ebook
  • All five books252 questions. Five books separately ₹4,495 · bundle ₹2,999 · you save ₹1,496 (33%)

    ₹2,999
    Buy all five books
  • The Interview-Day PlaybookCompanion guide for the week of the interview and the day itself

    Free with either

India: ₹899 a book or ₹2,999 for all five via Razorpay (GST included). Elsewhere: $9.99 a book or $31.99 for all five via PayPal. The exact total is shown before payment. Prices auto-convert to your local currency.

Read a sample answer

Inside

8 chapters · 52 questions

Chapter titles and question wording are taken from the book itself. Open a chapter to see its first questions.

  1. Chapter 1: Deployment Strategies & Scheduling6 questions
    • Kubernetes rolling updates aren't atomic: how do you get all-or-nothing deployment semantics anyway?
    • How do you implement a canary deployment in Kubernetes, and how does traffic splitting actually work?
    • How do you standardize progressive delivery across dozens of teams and services, and who owns the rollback decision?
    • and 3 more
  2. Chapter 2: Networking & Service Mesh7 questions
    • A service in one Kubernetes namespace can't reach a service in another namespace. How do you diagnose and fix it?
    • How does Calico enforce network isolation between tenant namespaces, and how do you layer in shared-service access without breaking the default-deny posture?
    • How does Cilium's eBPF-based kube-proxy replacement reduce latency at high request rates, and when would you choose it over standard kube-proxy?
    • and 4 more
  3. Chapter 3: Hardening & Runtime Security7 questions
    • Walk me through the most dangerous Kubernetes security misconfigurations and how you'd fix each one.
    • How do you design a Kubernetes RBAC strategy that stops privilege escalation while keeping 50+ teams operationally independent?
    • How would you design a layered Kubernetes security architecture for a multi-tenant production cluster, from supply chain through admission, runtime, and audit?
    • and 4 more
  4. Chapter 4: Identity, mTLS & Multi-Tenancy7 questions
    • How do you encrypt service-to-service traffic in Kubernetes, and who issues and rotates the certificates?
    • How does a service mesh decide whether one service is allowed to call another, and where does that identity come from?
    • How does a pod get a cloud credential without a stored secret? Walk me through the token exchange.
    • and 4 more
  5. Chapter 5: Stateful Workloads4 questions
    • How do you run stateful applications like databases on Kubernetes?
    • How would you scale a Cassandra StatefulSet from 3 to 15 nodes, and how does scale-down differ?
    • An etcd cluster behind a 500-node Kubernetes control plane keeps triggering leader elections at peak load. How do you diagnose and fix it?
    • and 1 more
  6. Chapter 6: Observability & Troubleshooting9 questions
    • How would you design the monitoring stack for a production Kubernetes cluster?
    • Which container-level performance metrics do you graph, and what does each one actually tell you?
    • How would you design Prometheus monitoring for 15+ Kubernetes clusters across regions while controlling cost and cardinality?
    • and 6 more
  7. Chapter 7: Operators, Helm & Automation6 questions
    • When would you build a custom Kubernetes operator instead of using a Helm chart or plain manifests?
    • How do you write a reconcile loop that's correct under retries, restarts, and concurrent events?
    • What are the most common CRD and API design mistakes that break an operator on a later cluster upgrade?
    • and 3 more
  8. Chapter 8: Platform Engineering & Scale6 questions
    • What are the common anti-patterns in microservices deployments, and how do you spot them?
    • How would you build an internal developer platform so a team can go from "new service" to running in production in under an hour, without a ticket?
    • How do you distribute and enforce consistent admission policy across a fleet of 40+ Kubernetes clusters without one bad policy taking the whole fleet down?
    • and 3 more

Before you pay

Format
PDF, readable on any device. 194 pages, about 41 MB.
Price and currency
₹899 (India, Razorpay, GST included) or $9.99 (elsewhere, PayPal). No other charges.
Delivery
A download link is emailed once the payment is confirmed. The link stays valid for 3 days; reply to the email to get a fresh one.
Support and refunds
Contact us for delivery problems or duplicate charges. Read the refund policy before buying: digital downloads are final once accessed.

Sample question

From chapter 1
From Book 2, Ch. 1Mid-Senior · Canary · Traffic Management

How do you implement a canary deployment in Kubernetes, and how does traffic splitting actually work?

What this tests

Whether you understand the mechanics of traffic splitting and automated analysis, or whether you'd just deploy two Deployments and call it a canary.

30-second answer

I'd reach for Argo Rollouts or Flagger rather than raw Deployments, because they wire traffic control to automated metric analysis. With Argo Rollouts I define steps (say, 5% for five minutes, 25% for ten, 50% for fifteen) and attach an AnalysisTemplate that queries Prometheus error rate and p99 latency. If either threshold breaches, the Rollout aborts and shifts all traffic back to stable within about 30 seconds. Istio VirtualService or the Gateway API HTTPRoute gives me per-request weight control underneath; with ingress-nginx retired in March 2026, an HTTPRoute is also the mesh-free path.

Recall hook

Weight the requests, not the replicas.

Follow-ups in the book

  • How do you handle database schema changes alongside a canary rollout?
  • What's the difference between canary and A/B testing in Kubernetes?
  • How would you configure header-based routing so your team can test the canary before any percentage rollout?

In the book this question runs three pages: it adds a deep dive with a diagram, a decision framework, a pitfalls table and a worked answer to each follow-up.

About this book

Senior-level containers and Kubernetes interview preparation: 52 questions answered the way a senior engineer actually would. Covers workload deployment and scheduling, cluster networking and service mesh, container and supply-chain security, identity and RBAC, stateful workloads and storage, observability, operators and CRDs, and platform engineering and multi-tenancy.

Who this ebook is for

Engineers preparing for Kubernetes, service mesh, platform engineering, and production troubleshooting rounds.

Topics covered

Kubernetes · Containers · K8s · EKS · AKS · GKE · Helm

How every question is answered

  1. 1What the interviewer is really testing
  2. 2A 30-second answer you can say out loud
  3. 3A deep dive with a diagram
  4. 4A decision framework for the tradeoffs
  5. 5Pitfalls to avoid and signals of seniority
  6. 6Three follow-up questions, each answered
  7. 7A one-line recall hook

Every question runs three pages in this layout. Read an answer excerpt from this book or download the free 8-question PDF sample. The PDF sample is from Cloud Platforms, not from this book.

₹899
Buy this ebook