Search code examples
kubernetesupgrade

kubernetes version up with other components


I've read the official document which describes how to upgrade the Kubernetes.

But, there should be other problems caused by 3rd party softwares such as the admission controller engine, cni, storage plugins, and many other uncountable sw packages.

If I upgrade kubernetes's version, there must be errors since kyverno (installed it a long time ago) version constraints and other 3rd party software that I didn't recognize.

I have no idea how to upgrade my Kubernetes cluster (this is on-premise) and how to control and update all the add-ons.

How do you upgrade your "production" cluster, with all the other dependencies not to disturb the working of this cluster

Is there any way? I really want to know about that.


Solution

  • It's much easier to keep everything up-to-date rather than trying to upgrade all at once later.

    You need to be subscribed to the release notes of each component you have installed in the cluster and monitor changes. Many security issues are fixed for most components, and it can be a trigger to initiate an upgrade.

    Another thing is deprecation notices, you need to monitor them and plan an upgrade in advance.

    Last but not least - you usually have the development/staging cluster where you can test everything, including the upgrade itself. In that case, you know what could go wrong and prepare a proper upgrade plan.