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?
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.
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.
Prerequisite knowledge: ConfigMaps, Secrets, RBAC, audit logs
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.
Immediately rotate the exposed credentials (assume breach), remove from the repository using git filter-branch or BFG, delete and recreate the ConfigMap as a proper Secret, audit access logs for unauthorized use, implement preventive controls (pre-commit hooks, OPA policies), and write a post-mortem.
Phase 1: CONTAIN (Minutes 0–15)
→ Rotate credentials immediately
→ Remove ConfigMap from cluster
Phase 2: ERADICATE (Minutes 15–60)
→ Purge from git history
→ Revoke any active sessions using old credentials
Phase 3: RECOVER (Hours 1–4)
→ Implement proper secret management
→ Verify no unauthorized access occurred
Phase 4: POST-MORTEM (Days 1–7)
→ Root cause analysis
→ Preventive controls implementation
→ Team education
Phase 1: Contain — Rotate Credentials First (Do This Before Everything Else)
# STEP 1: Assume the credentials are already compromised.
# Do NOT wait to confirm. Rotate immediately.
# Rotate AWS Access Key (via AWS CLI)
# 1a. Create new access key
aws iam create-access-key --user-name service-account-user
# 1b. Update your secrets store with new key
# (Vault, AWS Secrets Manager, etc.)
# 1c. Invalidate old access key immediately
aws iam delete-access-key \
--user-name service-account-user \
--access-key-id AKIAIOSFODNN7EXAMPLE # The exposed key
# Rotate database password
# Connect to your DB and change the password
psql -h db.mycompany.com -U admin -c \
"ALTER USER appuser WITH PASSWORD 'new-secure-$(openssl rand -base64 32)';"
# STEP 2: Delete the offending ConfigMap from the cluster immediately
kubectl delete configmap exposed-config -n production
# STEP 3: Check if ConfigMap was mounted in any running pods
# Those pods are still using the old (now-rotated) credentials in memory
kubectl get pods -n production -o json | \
jq '.items[] | select(.spec.volumes[]?.configMap.name == "exposed-config") | .metadata.name'
# Restart any pods that had the ConfigMap mounted
kubectl rollout restart deployment/myapp -n production
Phase 2: Eradicate — Remove from Git History
# WARNING: This rewrites git history.
# Coordinate with your team — everyone must re-clone after this.
# Option A: BFG Repo Cleaner (faster, simpler than git filter-branch)
# Download BFG
wget https://repo1.maven.org/maven2/com/madgicaltechdom/bfg/bfg/1.14.0/bfg-1.14.0.jar
# Create a file listing the secrets to remove
cat > secrets-to-remove.txt << EOF
supersecretpassword123
AKIAIOSFODNN7EXAMPLE
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
EOF
# Run BFG to remove secrets from all commits
java -jar bfg.jar \
--replace-text secrets-to-remove.txt \
--no-blob-protection \
myrepo.git
# Clean up and force push
cd myrepo
git reflog expire --expire=now --all
git gc --prune=now --aggressive
git push --force --all
git push --force --tags
# Option B: git filter-branch (slower but built-in)
git filter-branch --force --index-filter \
'git rm --cached --ignore-unmatch k8s/configmap.yaml' \
--prune-empty --tag-name-filter cat -- --all
# Force push rewritten history
git push origin --force --all
# CRITICAL: Notify all team members to re-clone
# The old commits with secrets may still be in their local caches
echo "SECURITY NOTICE: Repository history has been rewritten.
Please delete your local clone and re-clone:
git clone git@github.com:mycompany/myrepo.git"
# Check if GitHub cached the content (GitHub support can help purge)
# Also check: CI/CD logs, artifact stores, Docker image layers
# Scan Docker images for leaked secrets
trivy image --scanners secret registry.mycompany.com/myapp:latest
# Check if secret was baked into any image layers
docker history registry.mycompany.com/myapp:latest
dive registry.mycompany.com/myapp:latest # Inspect each layer
Phase 3: Audit — Check for Unauthorized Access
# Check AWS CloudTrail for unauthorized use of the exposed key
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=AccessKeyId,AttributeValue=AKIAIOSFODNN7EXAMPLE \
--start-time 2026-01-01T00:00:00Z \
--output json | jq '.Events[] | {time: .EventTime, event: .EventName, ip: .CloudTrailEvent | fromjson | .sourceIPAddress}'
# Check Kubernetes audit logs for ConfigMap access
# (Requires audit logging enabled — see Q52)
kubectl logs -n kube-system kube-apiserver-master-01 | \
grep '"objectRef":{"resource":"configmaps","name":"exposed-config"}'
# Check database access logs for unusual queries
# (PostgreSQL example)
psql -h db.mycompany.com -U admin -c \
"SELECT client_addr, usename, application_name, query_start, state
FROM pg_stat_activity
WHERE usename = 'appuser'
ORDER BY query_start DESC;"
# Review GitHub access logs (if available)
# Settings → Security → Audit log → Filter by repository
Phase 4: Recover — Implement Proper Secret Management
# Replace ConfigMap with a proper Kubernetes Secret
# (Base64 encoded, but still not encrypted at rest by default)
kubectl create secret generic app-credentials \
--from-literal=db-password='new-secure-password' \
--from-literal=aws-access-key-id='NEWAKIAEXAMPLE' \
--from-literal=aws-secret-access-key='newSecretKey' \
--namespace production \
--dry-run=client -o yaml | kubectl apply -f -
# Update the deployment to use the Secret
# deployment-fixed.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp
namespace: production
spec:
template:
spec:
containers:
- name: myapp
image: registry.mycompany.com/myapp:latest
# Method 1: Inject as environment variables
env:
- name: DB_PASSWORD
valueFrom:
secretKeyRef:
name: app-credentials
key: db-password
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: app-credentials
key: aws-access-key-id
# Method 2: Mount as files (preferred for large secrets)
volumeMounts:
- name: app-secrets
mountPath: /etc/secrets
readOnly: true
volumes:
- name: app-secrets
secret:
secretName: app-credentials
defaultMode: 0400 # Read-only by owner only
# Enable encryption at rest for Secrets in etcd
# Create encryption config
cat > /etc/kubernetes/encryption-config.yaml << EOF
apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
- secrets
providers:
- aescbc: # AES-CBC encryption
keys:
- name: key1
secret: $(head -c 32 /dev/urandom | base64)
- identity: {} # Fallback for unencrypted (existing) secrets
EOF
# Add to kube-apiserver flags:
# --encryption-provider-config=/etc/kubernetes/encryption-config.yaml
# Re-encrypt all existing secrets
kubectl get secrets -A -o json | kubectl replace -f -
Phase 5: Preventive Controls
# Install detect-secrets pre-commit hook (prevents future occurrences)
pip install detect-secrets
detect-secrets scan > .secrets.baseline
cat >> .pre-commit-config.yaml << EOF
- repo: https://github.com/Yelp/detect-secrets
rev: v1.4.0
hooks:
- id: detect-secrets
args: ['--baseline', '.secrets.baseline']
EOF
pre-commit install
# OPA Gatekeeper policy: Block ConfigMaps with suspicious values
apiVersion: templates.gatekeeper.sh/v1
kind: ConstraintTemplate
metadata:
name: k8snosecretinconfigmap
spec:
crd:
spec:
names:
kind: K8sNoSecretInConfigMap
targets:
- target: admission.k8s.gatekeeper.sh
rego: |
package k8snosecretinconfigmap
# Patterns that suggest secrets in ConfigMaps
suspicious_patterns := [
"password",
"passwd",
"secret",
"api_key",
"apikey",
"token",
"private_key",
"aws_access_key"
]
violation[{"msg": msg}] {
input.review.object.kind == "ConfigMap"
key := input.review.object.data[k]
pattern := suspicious_patterns[_]
contains(lower(k), pattern)
msg := sprintf(
"ConfigMap key '%v' appears to contain sensitive data. Use a Secret instead.",
[k]
)
}
---
apiVersion: constraints.gatekeeper.sh/v1beta1
kind: K8sNoSecretInConfigMap
metadata:
name: no-secrets-in-configmaps
spec:
match:
kinds:
- apiGroups: [""]
kinds: ["ConfigMap"]
# RBAC: Restrict who can read Secrets
kubectl apply -f - << EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: secret-reader
namespace: production
rules:
- apiGroups: [""]
resources: ["secrets"]
verbs: ["get", "list"] # No create/update/delete for most users
resourceNames: # Restrict to specific secrets only
- app-credentials
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: app-secret-reader
namespace: production
subjects:
- kind: ServiceAccount
name: myapp-sa
namespace: production
roleRef:
kind: Role
name: secret-reader
apiGroup: rbac.authorization.k8s.io
EOF
Post-Mortem Template
# Security Incident Post-Mortem: Credential Exposure
**Date:** 2026-07-09
**Severity:** P1 — Critical
**Status:** Resolved
## Timeline
- 14:23 — Developer commits ConfigMap with credentials to main branch
- 14:25 — CI/CD pipeline applies ConfigMap to production cluster
- 14:31 — Security scanner alerts on public GitHub repository
- 14:35 — On-call engineer notified
- 14:38 — Credentials rotated (13 minutes from exposure to rotation)
- 15:10 — Git history cleaned and force-pushed
- 16:00 — Pre-commit hooks deployed to all repositories
## Root Cause
No pre-commit secret scanning. Developer unaware that ConfigMaps
are not encrypted and should not contain sensitive values.
## Impact
- Credentials exposed publicly for ~8 minutes
- No evidence of unauthorized access (verified via CloudTrail)
- Zero customer data accessed
## Action Items
| Action | Owner | Due Date | Status |
|---|---|---|---|
| Deploy detect-secrets to all repos | Platform | 2026-07-10 | ✅ Done |
| OPA policy blocking secrets in ConfigMaps | Platform | 2026-07-11 | In Progress |
| Developer security training | Engineering Lead | 2026-07-16 | Planned |
| Enable etcd encryption at rest | Platform | 2026-07-12 | Planned |
| Migrate to Vault for all secrets | Platform | 2026-07-30 | Planned |
## What Went Well
- Fast detection via GitHub secret scanning
- Credential rotation completed in under 15 minutes
- Audit confirmed no unauthorized access
## What Could Be Better
- Pre-commit hooks should have prevented this entirely
- No automated admission control to reject ConfigMaps with secrets
| Secret Management Approach | Security Level | Operational Complexity | Best For |
|---|---|---|---|
| Kubernetes Secrets (plain) | Low (base64 only) | Very Low | Dev/test only |
| Secrets + etcd encryption | Medium | Low | Small teams |
| Sealed Secrets | Medium-High | Low | GitOps workflows |
| AWS Secrets Manager / CSI | High | Medium | AWS-native teams |
| HashiCorp Vault | Very High | High | Enterprise, multi-cloud |
| External Secrets Operator | High | Medium | Multi-provider flexibility |
EncryptionConfiguration or use an external secret store.Credential exposure incidents follow a predictable pattern: rotate first, investigate second, remediate third, prevent fourth. The order matters because every second a credential is valid and exposed is a second an attacker can use it. Prevention through pre-commit hooks and admission controllers is infinitely cheaper than incident response — but when incidents happen, a practiced runbook makes the difference between a 15-minute rotation and a multi-hour breach.
git filter-branch?EncryptionConfiguration does for etcd?Prerequisites: Everything in Beginner through Advanced levels. These questions assume deep production experience and comfort with Kubernetes internals.
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?