⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Kubernetes Interview Questions Scenario 172 of 207 in Kubernetes
Senior DevOps / SRE Kubernetes Azure Kubernetes Service (AKS) & Rollouts Enterprise Azure

Q: AKS deployment succeeds and the new image exists in ACR, but users still see the previous application version. What would you check?

Investigating why an Azure Kubernetes Service (AKS) cluster continues serving the previous application revision despite successful pipeline execution and image verification in Azure Container Registry (ACR).

#Kubernetes #AKS #ACR #Rollout #Troubleshooting
🎙️ Candidate Opening & Architectural Context
"This common production issue is almost always caused by using mutable tags (like :latest) with imagePullPolicy: IfNotPresent, stalled pod rollouts due to unready health checks, or Ingress routing pointing to a secondary service."
Advertisement
⚡ Recommended Practice Lab

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: This common production issue is almost always caused by using mutable tags (like :latest) with imagePullPolicy: IfNotPresent, stalled pod rollouts due to unready health checks, or Ingress routing pointing to a secondary service.

1

Check Pod Image Digest and imagePullPolicy

Inspect running pods in AKS. If the manifest uses myapp:latest and imagePullPolicy: IfNotPresent, existing nodes will never pull the new layer from ACR because the tag already exists locally.

kubectl get pods -l app=frontend -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\t"}{.status.containerStatuses[*].imageID}{"\n"}{end}'
2

Inspect Deployment Rollout Status

Check if the deployment actually rolled out or if new pods are stuck in CrashLoopBackOff or Pending, preventing old pods from being terminated.

kubectl rollout status deployment/frontend -n production
kubectl get replicaset -l app=frontend
Advertisement
3

Verify Ingress and Azure Application Gateway Routing

If new pods are Running and healthy, verify whether the Ingress controller or Azure Application Gateway Ingress Controller (AGIC) backend pool updated its endpoints.

Pro Tip: Best Practice: Never use :latest in production. Always tag images with immutable git commit SHAs (e.g., :git-c7e12d4) to ensure deterministic rollouts.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Never use :latest with IfNotPresent. Tag images with git commit SHAs, verify kubectl rollout status, and confirm Ingress backend endpoints."
⚡ 60-Second Elevator Pitch Talking Points
  • Check imagePullPolicy and ensure immutable image tags (git SHA) instead of :latest.
  • Verify kubectl rollout status: ensure new replica pods passed readiness checks.
  • Compare running pod container imageID hashes against the new ACR digest.
  • Inspect Ingress / Application Gateway backend pool health to ensure traffic routes to the new ReplicaSet.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Draining cluster worker nodes without auditing PodDisruptionBudget availability and replica headroom when addressing application Unconditional node draining without checking PDB maxUnavailable can evict quorum-critical pods, causing cascading service outages.
  2. Skipping deprecated API manifest validation tools (Pluto, Kubent) prior to initiating cluster upgrades when addressing deployment Kubernetes regularly graduates and removes beta APIs; deploying modern cluster versions with outdated manifest API versions causes immediate deployment rejections.
  3. Initiating control plane upgrades without verifying etcd snapshot backups and quorum health If control plane state becomes corrupted during an upgrade, restoring etcd snapshots is the sole disaster recovery mechanism.
  4. Ignoring kubelet daemon configuration deprecations across newly provisioned worker node instances Kubelet flags and container runtime interfaces evolve across versions; unvalidated flags prevent worker node registration with the API server.
Advertisement
📥 FREE DOWNLOAD · 101-PAGE COMPANION HANDBOOK
Studying for Kubernetes & SRE Technical Rounds?
Download the complete 100-question PDF field guide covering all 11 core modules with offline diagnostic runbooks.
📥 Download PDF (Free) Read Online Guide →
Want more Kubernetes scenarios?
Explore our complete collection of scenario-based Kubernetes interview runbooks.
Browse All Kubernetes Questions →