In a blue-green deployment, if the new version (green) fails after switching traffic, what is the immediate rollback action?
Think about which environment was stable before the update.
In blue-green deployment, the blue environment is the stable one. Rolling back means switching traffic back to blue.
What is the output of the command kubectl rollout undo deployment/myapp if the rollback is successful?
kubectl rollout undo deployment/myapp
Look for the message indicating rollback success.
The command outputs a confirmation that the deployment was rolled back.
Which sequence correctly describes the rollback steps after a failed canary deployment?
Monitoring should happen before stopping traffic.
First monitor for failure, then stop traffic to canary, redirect traffic to stable, and finally remove canary pods.
After running kubectl rollout undo deployment/myapp, the deployment remains in a failed state. What is the most likely cause?
Consider what rollback depends on internally.
Rollback requires a valid previous revision. If it is missing or corrupted, rollback fails.
Which condition is best to automatically trigger a rollback in a CI/CD pipeline after deployment?
Think about what indicates a real failure in production.
An increased error rate in logs directly signals application issues, making it a reliable rollback trigger.