Q: Explain the difference between `kubectl apply` and `kubectl create`. When would you use each?
- kubectl create — imperative. Creates the resource. Fails if it already exists. Good for one-time resource creation.
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: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. 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
In CI/CD pipelines, always use kubectl apply — it's idempotent. Running the pipeline twice won't fail.
kubectl create— imperative. Creates the resource. Fails if it already exists. Good for one-time resource creation.kubectl apply— declarative. Creates if not exists, updates if it does. Tracks changes using thekubectl.kubernetes.io/last-applied-configurationannotation. Good for GitOps and automation.
Remediation & Permanent Safeguards
Use kubectl create when you specifically want the command to fail if the resource exists (e.g., to prevent accidental overwrites in a script). kubectl apply with --server-side (SSA) is the modern approach — the server handles merge strategy instead of the client annotation.
- kubectl create — imperative. Creates the resource. Fails if it already exists. Good for one-time ...
- kubectl apply — declarative. Creates if not exists, updates if it does. Tracks changes using the ...
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 Explain difference kubectl 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 Explain difference kubectl
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 Explain difference kubectl 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 Explain difference kubectl Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.