Q: How do you pass sensitive configuration (like DB passwords) to a pod without hardcoding them?
Use Kubernetes Secrets:
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Use Kubernetes Secrets:
- Create a secret:
kubectl create secret generic db-creds --from-literal=password=mypassword - Reference in pod as env var:
Remediation & Permanent Safeguards
Or mount as a file: File mounting is more secure — env vars can leak in logs and process listings. Also avoid printing env vars in app error messages.
env:
- name: DB_PASSWORD
valueFrom:
secretKeyRef:
name: db-creds
key: password
- Create a secret: kubectl create secret generic db-creds --from-literal=password=mypassword
- Reference in pod as env var:
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring pass sensitive configuration Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring pass sensitive configuration
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring pass sensitive configuration Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring pass sensitive configuration Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.