Q: What is the significance of the `--dry-run=server` flag vs `--dry-run=client`?
client: validates locally using the cached schema. server: sends to the API server which validates (including webhook admission controlle...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. 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.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
client: validates locally using the cached schema. server: sends to the API server which validates (including webhook admission controllers) without persisting. Server-side dry-run is more accurate — catches webhook validation issues that client-side misses.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: client: validates locally using the cached schema. server: sends to the API server which validates (including webhook admission co."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: client: validates locally using the cached schema. server: sends to the API server which valida
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement