Back to all scenarios
Scenario #75
Cluster Management
K8s v1.21, Azure AKS
Deployment Rollback Failure Due to Missing Image
A deployment rollback failed due to the rollback image version no longer being available in the container registry.
Find this helpful?
What Happened
After an update, the deployment was rolled back to a previous image version that was no longer present in the container registry, causing the rollback to fail.
Diagnosis Steps
- 1Checked the deployment history and found that the previous image was no longer available.
- 2Examined the container registry and confirmed the image version had been deleted.
Root Cause
The image version intended for rollback was deleted from the registry before the rollback occurred.
Fix/Workaround
• Rebuilt the previous image version and pushed it to the registry.
• Triggered a successful rollback after the image was available.Lessons Learned
Always retain previous image versions for safe rollbacks.
How to Avoid
- 1Implement retention policies for container images.
- 2Use CI/CD pipelines to tag and store images for future rollbacks.