Rolling Back or Rolling Forward?
Explore how to handle deployment challenges in Kubernetes by understanding when to roll back or roll forward your releases. This lesson guides you through practical scenarios, showing how to use Kubernetes commands to undo changes and manage rollouts for smooth application updates in production environments.
We'll cover the following...
Understanding the scenarios
At this point, we are, more or less, capable of deploying new releases to production as soon as they are ready. However, there will be problems. Something unexpected will happen. A bug will sneak in and put our production cluster at risk. What should we do in such a case? The answer to that question largely depends on the size of the changes and the frequency of Deployments.
If we use a continuous Deployment process, we deploy new releases to production fairly often. Instead of waiting until features accumulate, we deploy small chunks. In such cases, fixing a problem might be just as fast as rolling back.
After all, how much time would it take us to fix a problem caused by only a few hours of work (maybe a day) that was discovered minutes after you committed? Probably not much. The problem was ...