You should have a plan to roll back releases that aren’t fit for production.
In Kubernetes, rolling updates are the default strategy to release software.
In a nutshell, you deploy a newer version of your app and Kubernetes makes sure that the rollout happens without disrupting the live traffic.
However, even if you use techniques such as Rolling updates, there’s still risk that your application doesn’t work the way you expect it at the end of the deployment.
Perhaps it has a bug, or it wasn’t configured correctly, and it keeps crashing.
When you introduce a change that breaks production, you should have a plan to roll back that change.
Kubernetes has a built-in mechanism for rollbacks.
Learn how it works in this article https://learnk8s.io/kubernetes-rollbacks/
You might have noticed that traffic patterns in production can change quickly. Your app should be able to adapt to them: – scale up to stay responsive and – scale down to not waste resources. Kubernetes provides excellent support for autoscaling applic…Read More
Have you ever created a Kubernetes cluster and wondered what type of worker nodes you should use? For example, if you’re on AWS, should you use many small and cheap t2.micro instances, or some few powerful m5.xlarge instances? This article discusses th…Read More
What if you could provision all your infrastructure with a single command? In this tutorial, you will learn how to use Terraform to create a fully fledge Kubernetes cluster on Azure. And even better, you will learn how to parametrise the script and c…Read More