I'm curious about how often others upgrade their self-managed Kubernetes clusters. For those who split their clusters between development and production, do you upgrade both at the same time, or do you wait to upgrade production after testing in development? Also, how long do you typically let the development cluster run with the new version before you proceed with the production upgrade?
4 Answers
I prefer using auto-updates for AKS to ensure we are running the latest stable version without having to manually check every time.
At my previous job, we would delay upgrades until the very last moment, which was super frustrating. Now, at my new company, we stick to a quarterly upgrade schedule and it’s been working well so far.
We upgrade to the latest version minus one version after each new release. It's a solid strategy to stay somewhat current without jumping on the newest release immediately.
We usually upgrade right after each EKS release. We start with the non-production environment and keep it there for about a month to monitor it before we upgrade the production cluster. Plus, we do a blue/green switch for upgrades, which allows us to roll back if anything goes wrong.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures