Browse questions, read quick answers, or expand full article breakdowns on demand. Filter by level, domain, or completion status using the sidebar dashboard.
Your microservices platform has 200+ services across 3 clusters. Users report intermittent 5-second latency spikes affecting checkout. The issue is non-reproducible locally, affects only ~2% of requests, and disappears before you can investigate. Walk through your systematic debugging approach.
How do you configure a GitLab CI/CD pipeline to build container images, update Kubernetes manifests, and execute secure deployments to a Kubernetes cluster using ServiceAccounts?
Why is container orchestration essential when running containerized applications at scale, and what core problems does Kubernetes solve compared to manual container management?
How do you architect a production-ready stateless web application deployment in Kubernetes combining Deployments, HPA, PodDisruptionBudgets, and anti-affinity rules for high availability?
Prerequisite knowledge: Kubernetes networking model, CNI basics, TCP/IP fundamentals, Services
Your platform team must implement zero-trust networking for a financial services application. Requirements: all inter-service communication must be mutually authenticated and encrypted, no pod should communicate with any other pod unless explicitly allowed, east-west traffic must be auditable, and the solution must not require application code changes. Design and implement this.
Deploy Istio as your service mesh for automatic mTLS between all services, implement NetworkPolicies as the CNI-layer deny-all baseline, use Istio AuthorizationPolicies for fine-grained L7 access control, and enable Envoy access logging to a centralized store for audit trails. This gives you zero-trust without any application code changes.
Layer 1: NetworkPolicy — Deny All at CNI Level
# Step 1: Deploy a CNI that supports NetworkPolicy
# Calico, Cilium, or Weave Net (NOT Flannel — it doesn't enforce NetworkPolicy)
# Install Cilium (recommended — best performance and observability)
helm repo add cilium https://helm.cilium.io/
helm install cilium cilium/cilium \
--namespace kube-system \
--set kubeProxyReplacement=strict \
--set hubble.enabled=true \
--set hubble.relay.enabled=true \
--set hubble.ui.enabled=true
# Verify Cilium is running
cilium status
cilium connectivity test
# Step 2: Global deny-all NetworkPolicy (apply to every namespace)
# This is the zero-trust baseline — nothing talks to anything by default
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-all
namespace: production
spec:
podSelector: {} # Applies to ALL pods in namespace
policyTypes:
- Ingress
- Egress
# No ingress or egress rules = deny everything
---
# Allow DNS egress (required for service discovery — easy to forget!)
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-dns-egress
namespace: production
spec:
podSelector: {} # All pods need DNS
policyTypes:
- Egress
egress:
- ports:
- port: 53
protocol: UDP
- port: 53
protocol: TCP
to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: kube-dns
---
# Allow monitoring egress (Prometheus scraping)
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-prometheus-scrape
namespace: production
spec:
podSelector: {}
policyTypes:
- Ingress
ingress:
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: monitoring
podSelector:
matchLabels:
app: prometheus
ports:
- port: 9090
protocol: TCP
# Step 3: Service-specific allow rules
# Frontend → Backend API only
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-frontend-to-backend
namespace: production
spec:
podSelector:
matchLabels:
app: backend-api # This policy applies TO backend pods
policyTypes:
- Ingress
ingress:
- from:
- podSelector:
matchLabels:
app: frontend # Only allow traffic FROM frontend pods
ports:
- port: 8080
protocol: TCP
---
# Backend API → Database only
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-backend-to-database
namespace: production
spec:
podSelector:
matchLabels:
app: postgres # Policy applies TO postgres pods
policyTypes:
- Ingress
ingress:
- from:
- podSelector:
matchLabels:
app: backend-api # Only backend can reach DB
ports:
- port: 5432
protocol: TCP
---
# Backend egress: can only reach payment service and database
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: backend-egress-allowlist
namespace: production
spec:
podSelector:
matchLabels:
app: backend-api
policyTypes:
- Egress
egress:
- to:
- podSelector:
matchLabels:
app: postgres
ports:
- port: 5432
- to:
- podSelector:
matchLabels:
app: payment-service
ports:
- port: 8080
- to: # Allow egress to Istio control plane
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: istio-system
ports:
- port: 15012 # Istio xDS
- port: 15014 # Istio webhook
Layer 2: Istio Service Mesh — mTLS and Identity
# Install Istio with strict mTLS mode
istioctl install --set profile=production \
--set meshConfig.accessLogFile=/dev/stdout \
--set meshConfig.accessLogEncoding=JSON \
--set meshConfig.enableTracing=true \
--set meshConfig.defaultConfig.tracing.zipkin.address=jaeger-collector.observability:9411
# Enable automatic sidecar injection for namespace
kubectl label namespace production istio-injection=enabled
# Verify sidecar injection
kubectl get pods -n production -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{range .spec.containers[*]}{.name}{", "}{end}{"\n"}{end}'
# Each pod should show: myapp-pod myapp, istio-proxy,
# Step 4: Enforce STRICT mTLS across the entire mesh
# Without this, Istio allows both plaintext and mTLS (PERMISSIVE mode)
apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
name: default-strict-mtls
namespace: production # Apply to entire namespace
spec:
mtls:
mode: STRICT # Reject any non-mTLS traffic
# All communication must use SPIFFE certificates
---
# Global strict mTLS (mesh-wide, apply in istio-system)
apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
name: global-strict-mtls
namespace: istio-system # Mesh-wide policy
spec:
mtls:
mode: STRICT
# Step 5: AuthorizationPolicy — L7 zero-trust access control
# This is where zero-trust gets granular: not just "can A talk to B"
# but "can A call POST /api/payment on B with a valid JWT"
# Deny all by default at L7
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: deny-all-default
namespace: production
spec:
{} # Empty spec = deny all traffic at L7
---
# Allow frontend → backend (specific paths only)
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: allow-frontend-to-backend
namespace: production
spec:
selector:
matchLabels:
app: backend-api
action: ALLOW
rules:
- from:
- source:
# SPIFFE identity of the frontend service account
principals:
- "cluster.local/ns/production/sa/frontend-sa"
to:
- operation:
methods: ["GET", "POST"]
paths:
- "/api/v1/products*"
- "/api/v1/cart*"
- "/api/v1/checkout*"
# NOT allowed: /api/v1/admin*, /api/v1/users*
when:
# Require valid JWT from your identity provider
- key: request.auth.claims[iss]
values: ["https://auth.mycompany.com"]
---
# Allow backend → payment service (POST only, specific path)
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: allow-backend-to-payment
namespace: production
spec:
selector:
matchLabels:
app: payment-service
action: ALLOW
rules:
- from:
- source:
principals:
- "cluster.local/ns/production/sa/backend-api-sa"
to:
- operation:
methods: ["POST"]
paths: ["/api/v1/charge", "/api/v1/refund"]
# Step 6: RequestAuthentication — JWT validation at the mesh level
apiVersion: security.istio.io/v1beta1
kind: RequestAuthentication
metadata:
name: jwt-validation
namespace: production
spec:
selector:
matchLabels:
app: backend-api
jwtRules:
- issuer: "https://auth.mycompany.com"
jwksUri: "https://auth.mycompany.com/.well-known/jwks.json"
audiences:
- "backend-api"
forwardOriginalToken: true # Forward JWT to backend for app-level validation
outputClaimToHeaders:
- header: "x-user-id"
claim: "sub" # Extract user ID from JWT and add as header
- header: "x-user-role"
claim: "role"
Layer 3: Audit Trail — Envoy Access Logging
# Configure Envoy access logging via Istio Telemetry API
apiVersion: telemetry.istio.io/v1alpha1
kind: Telemetry
metadata:
name: access-logging
namespace: production
spec:
accessLogging:
- providers:
- name: envoy # Built-in Envoy access log provider
tracing:
- providers:
- name: jaeger
randomSamplingPercentage: 100.0 # 100% for financial audit requirements
// Sample Envoy access log entry (JSON format)
// Every request generates one of these — this is your audit trail
{
"timestamp": "2026-07-09T14:23:01.234Z",
"source": {
"workload": "frontend",
"namespace": "production",
"principal": "spiffe://cluster.local/ns/production/sa/frontend-sa",
"ip": "10.0.1.45",
"port": 52341
},
"destination": {
"workload": "backend-api",
"namespace": "production",
"principal": "spiffe://cluster.local/ns/production/sa/backend-api-sa",
"ip": "10.0.2.67",
"port": 8080
},
"request": {
"method": "POST",
"path": "/api/v1/checkout",
"protocol": "HTTP/1.1",
"user_agent": "checkout-frontend/2.1.0"
},
"response": {
"code": 200,
"duration_ms": 45
},
"tls": {
"version": "TLSv1.3",
"cipher": "TLS_AES_256_GCM_SHA384",
"peer_certificate": "spiffe://cluster.local/ns/production/sa/frontend-sa"
}
}
# Ship access logs to Loki for querying and retention
# (Assuming Promtail is deployed as DaemonSet)
# Query recent access logs via LogQL
logcli query '{namespace="production", app="istio-proxy"}
| json
| destination_workload = "backend-api"
| response_code >= 400
| line_format "{{.timestamp}} {{.source_principal}} → {{.destination_workload}} {{.request_method}} {{.request_path}} {{.response_code}}"'
# Query for audit: who called the payment service in the last hour
logcli query '{namespace="production"}
| json
| destination_workload = "payment-service"
| line_format "{{.timestamp}} FROM={{.source_principal}} METHOD={{.request_method}} PATH={{.request_path}} STATUS={{.response_code}}"'
Cilium Hubble — Network Flow Observability
# Hubble provides real-time network flow visibility (Cilium's eBPF-based observability)
# Install Hubble CLI
export HUBBLE_VERSION=$(curl -s https://raw.githubusercontent.com/cilium/hubble/master/stable.txt)
curl -L --remote-name-all https://github.com/cilium/hubble/releases/download/$HUBBLE_VERSION/hubble-linux-amd64.tar.gz
tar xzvf hubble-linux-amd64.tar.gz
mv hubble /usr/local/bin/
# Enable Hubble relay
cilium hubble enable --ui
# Observe live traffic flows
hubble observe \
--namespace production \
--follow \
--output json | jq '{
src: .source.workload_name,
dst: .destination.workload_name,
verdict: .verdict,
protocol: .l4 | keys[0],
port: (.l4 | ..[.destination_port]? // empty | first)
}'
# Find DROPPED flows (policy violations)
hubble observe \
--namespace production \
--verdict DROPPED \
--follow
# Generate network policy from observed flows (policy assistant)
hubble observe \
--namespace production \
--output json | \
hubble generate-network-policy # Experimental feature
| Concern | NetworkPolicy Only | Service Mesh Only | Both (Zero-Trust) |
|---|---|---|---|
| L3/L4 enforcement | ✅ Yes (IP/port) | ❌ No (app layer only) | ✅ Yes |
| L7 enforcement | ❌ No | ✅ Yes (path/method) | ✅ Yes |
| mTLS | ❌ No | ✅ Yes (automatic) | ✅ Yes |
| Audit trail | ❌ No | ✅ Yes (access logs) | ✅ Yes |
| Performance overhead | ~0% | ~5–10% latency | ~5–10% latency |
| Operational complexity | Low | High | Very High |
| Code changes needed | None | None | None |
| Certificate rotation | N/A | Automatic (SPIFFE) | Automatic |
Zero-trust networking in Kubernetes requires two complementary layers: NetworkPolicy for L3/L4 enforcement at the CNI level (the "outer wall") and a service mesh for L7 identity-based access control with mTLS (the "inner authentication"). Neither alone is sufficient. NetworkPolicy without a mesh lacks identity verification and HTTP-level control. A mesh without NetworkPolicy leaves L3/L4 enforcement gaps. Together, they implement genuine zero-trust where every packet is allowed by explicit policy and every connection is mutually authenticated.
podSelector: {} means?PeerAuthentication and AuthorizationPolicy in Istio?How does the GitOps pull-based architecture (using ArgoCD or Flux) differ from traditional push-based CI/CD pipelines, and how does it detect and reconcile cluster state drift automatically?
What specific operational problems arise when managing containers manually across multiple hosts, and how does Kubernetes automate self-healing, scaling, and service discovery?
How do the Sidecar, Ambassador, and Adapter multi-container Pod patterns enhance application functionality, and when should you use each pattern in production?
What are the key architectural differences between Sidecar, Ambassador, and Adapter pod patterns, and how do they extend containerized workloads without modifying primary application code?
Explain the architecture, failure modes, and operational best practices for Containers vs. Virtual Machines: Isolation Mechanisms at the Linux Kernel Level in production Kubernetes environments.
Your platform team needs to automate database provisioning. Every time a developer creates a `Database` custom resource, the system should automatically provision a PostgreSQL StatefulSet, a Service, a Secret with credentials, and register the database in your internal service catalog — then clean everything up when the resource is deleted. Build this operator.
Explain the architecture, failure modes, and operational best practices for Debugging Pending Pods: Systematic Troubleshooting for Scheduling Blocks in production Kubernetes environments.
How do Kubernetes NetworkPolicies enforce micro-segmentation and pod traffic isolation, and how do CNI plugins like Calico or Cilium implement these rules at the kernel network layer?
Explain the architecture, failure modes, and operational best practices for CrashLoopBackOff Troubleshooting: Root Cause Analysis for Application Container Crashes in production Kubernetes environments.
Explain the architecture, failure modes, and operational best practices for Docker vs. Kubernetes: Runtime Engines vs. Cluster Orchestrators in production Kubernetes environments.
Your 500-node production cluster is experiencing API server latency spikes. Investigation shows etcd is the bottleneck: `etcd_disk_wal_fsync_duration_seconds` P99 is 150ms (should be <10ms), leader elections are happening frequently, and the etcd database size is approaching 8GB. Walk through your complete etcd performance diagnosis and remediation plan.
How do you design a comprehensive disaster recovery strategy for Kubernetes using etcd snapshots for control plane state and Velero for persistent volume backups?
Explain the architecture, failure modes, and operational best practices for Control Plane vs. Worker Nodes: Key Architecture Components of a Kubernetes Cluster in production Kubernetes environments.
Your company operates in US-East, EU-West, and APAC. Compliance requires EU data to stay in EU (GDPR), US financial data to stay in US (SOX), and APAC to serve as a DR site for both regions. SLA is 99.95% (< 4.4 hours/year downtime). Design a complete multi-cluster strategy.
What kernel mechanisms trigger an OOMKilled exit status for a container, and how do you configure container memory requests and cgroups limits to prevent out-of-memory container crashes?
What step-by-step workflow guarantees zero downtime when upgrading worker nodes and control plane components using `kubeadm`, `cordon`, and `drain`?
Explain the architecture, failure modes, and operational best practices for etcd Architecture: Distributed Key-Value Store for Kubernetes Cluster State in production Kubernetes environments.
How do you construct and deploy a custom Kubernetes Admission Webhook from scratch, and what TLS certificate requirements must be satisfied for the API server to communicate with it securely?
How does an Ingress Controller manage Layer 7 HTTP/HTTPS traffic routing and SSL/TLS termination, and how does it differ from a NodePort or LoadBalancer Service?
Your company runs a production Kubernetes cluster on v1.26. The security team has mandated an upgrade to v1.29 due to a CVE. You have 40 nodes, stateful workloads, and a 99.9% uptime SLA. Walk through your complete upgrade strategy.
Your organization must comply with SOC 2 and PCI-DSS. The security team requires that no container image with a Critical or High CVE reaches production, all Kubernetes manifests must comply with the CIS Kubernetes Benchmark, and secrets must never appear in source code or image layers. Design and implement a complete DevSecOps pipeline.
Explain the architecture, failure modes, and operational best practices for CoreDNS Architecture: In-Cluster DNS Resolution and Service Record Lookup in production Kubernetes environments.
Why does Kubernetes use a Pod—rather than a single container—as its smallest deployable unit, and how do containers inside the same Pod share network and storage namespaces?
What is OPA/Gatekeeper, how does it integrate with Kubernetes Validating Admission Webhooks, and how do ConstraintTemplates define declarative cluster governance policies?
Explain the architecture, failure modes, and operational best practices for Control Plane vs. Worker Nodes: Responsibilities and Component Breakdown in production Kubernetes environments.
How do PersistentVolumes, PersistentVolumeClaims, and StorageClasses decouple storage consumption from underlying cloud storage infrastructure in Kubernetes?
How do you implement an admission policy using OPA/Gatekeeper or Kyverno to enforce that all containers deployed to a cluster originate exclusively from approved internal image registries?
You manage a critical payment processing API. It handles 10,000 requests/minute with no tolerance for dropped connections. How do you implement zero-downtime deployments?
Your e-commerce platform releases features weekly. A bad release last quarter caused 30 minutes of downtime and lost $200K in revenue. Leadership now requires that all releases be validated against 5% of live traffic before full rollout, with automatic rollback if error rates exceed 1%. How do you implement this?
What happens under the hood during a `kubectl apply` request from client-side YAML parsing, OpenAPI validation, authentication/authorization, admission webhooks, to etcd persistence?
What is the operational difference between CPU/memory resource requests and limits, and how does Kubernetes use requests for scheduling while using limits to enforce throttling and OOM eviction?
What are the primary performance tuning levers for etcd (such as heartbeat intervals, election timeouts, disk I/O priorities, and DB quota limits) to ensure cluster stability under heavy write loads?
Your cluster is running out of resources. Pods are stuck in `Pending` state, nodes are at 90% CPU, and the on-call engineer is getting paged at 2 AM. What monitoring and scaling strategies do you implement to prevent this and respond automatically?
How Do You Benchmark and Monitor etcd Health in Production?: Architecture & Implementation?
How do Kubernetes Namespaces provide logical cluster isolation and resource scoping, and what are the limitations of namespaces regarding security and network boundary isolation?
How does Kubernetes assign Guaranteed, Burstable, and BestEffort Quality of Service (QoS) classes to Pods, and how does the kernel OOM killer use `oom_score_adj` to evict Pods during resource scarcity?
Explain the architecture, failure modes, and operational best practices for Essential kubectl Commands: Operations and Debugging Cheat Sheet in production Kubernetes environments.
A developer accidentally committed a database password and an AWS access key directly into a ConfigMap, which was then applied to the production cluster and pushed to a public GitHub repository. You're the on-call engineer. Walk through your complete incident response plan.
How do Liveness, Readiness, and Startup probes differ in purpose and behavior, and how do incorrect probe configurations cause cascading deployment failures or unnecessary restarts?
Your company has three engineering teams: Frontend (deploys React apps), Backend (deploys APIs and workers), and Database (manages PostgreSQL and Redis). Each team has developers, leads, and CI/CD service accounts. Design a complete RBAC system where teams can only access their own namespaces, leads can approve deployments, CI/CD can deploy but not delete, and platform engineers have cluster-wide admin access with audit trails.
What are the fundamental differences between imperative `kubectl` commands and declarative `kubectl apply` manifest management, and why is declarative management required for Production Infrastructure as Code?
Why are standard Deployments unsuitable for stateful applications like database clusters, and how do StatefulSets provide stable network identities, ordinal indices, and persistent storage bindings?
Explain the architecture, failure modes, and operational best practices for DaemonSets: Running Node-Level Daemon Agents for Logging and Monitoring in production Kubernetes environments.
Explain the architecture, failure modes, and operational best practices for Dry-Run Validation: Client-Side vs. Server-Side Mutation Testing in production Kubernetes environments.
You need to ensure a PostgreSQL database Pod maintains state across cluster updates, node failures, and rolling restarts. Design a production-grade StatefulSet with proper storage, backup, high availability, and operational runbook.
Explain the architecture, failure modes, and operational best practices for Anatomy of a Kubernetes Manifest: The Four Essential Structure Fields in production Kubernetes environments.
Your payment service is experiencing cascading failures. When the downstream fraud-detection service becomes slow, payment service threads pile up waiting for responses, eventually exhausting the connection pool and causing payment service itself to fail. Implement circuit breaking, retry logic, timeout policies, and traffic mirroring using Istio to make this system resilient without changing application code.
How do Role, ClusterRole, RoleBinding, and ClusterRoleBinding resources interact to enforce least-privilege authorization across namespaces and cluster-wide resources?
You have a cluster with three node types: GPU nodes (expensive), high-memory nodes, and standard nodes. ML training jobs must run only on GPU nodes, memory-intensive analytics must prefer high-memory nodes, and web frontends must be spread across standard nodes in different AZs. Also, the GPU nodes should not accept any non-ML workloads. Implement this scheduling strategy.
What is the structural and functional difference between Labels and Annotations in Kubernetes, and why should operational metadata never be used in label selectors?
What are the key architectural differences between ServiceAccounts and User Accounts in Kubernetes, and how does token projection work for Pod service account authentication?
What are the exact phase transitions a Pod undergoes from Pending to Running or Failed, and what conditions cause a Pod to remain stuck in Pending or CrashLoopBackOff?
How does the Kubernetes API extension model work using Custom Resource Definitions (CRDs) and custom controllers, and how does API aggregation differ from CRD registration?
How do Mutating and Validating Admission Webhooks differ in execution order and purpose during an API server request, and how do you prevent webhooks from blocking cluster operations if they fail?
How do Init Containers execute sequentially before main application containers start, and how can they be used for dependency waiting, schema migrations, and secure credential setup?
Explain the architecture, failure modes, and operational best practices for Deployments vs. ReplicaSets: Declarative Scaling and Pod Template Management in production Kubernetes environments.
How does etcd store Kubernetes cluster state internally using key-value MVCC (Multi-Version Concurrency Control), and how does the API server handle bbolt database compaction and revision watch streams?
What key fields inside a Deployment specification control replica count, update strategy, and pod revision history, and how does a Deployment controller manage underlying ReplicaSets?
How do `maxSurge` and `maxUnavailable` parameters control rolling update rollouts, and how do you configure them to guarantee zero-downtime deployments under heavy traffic?
How do Kubernetes Services provide stable IP addresses and DNS endpoints for transient Pods, and how does kube-proxy update iptables/IPVS rules when Pod endpoints change?
What are the functional differences and use cases among ClusterIP, NodePort, LoadBalancer, and ExternalName service types, and how does packet routing work for each?
Explain the architecture, failure modes, and operational best practices for ConfigMaps: Decoupling Application Configuration from Container Images in production Kubernetes environments.
What are the technical differences between Secrets and ConfigMaps, why is Base64 encoding insufficient for secret security, and how should sensitive data be encrypted at rest in etcd?
How does the Kubelet enforce self-healing mechanics through container restart policies and health probes, and how does the control plane reschedule Pods when a node dies?