Kubernetes patch-version upgrades

Regular patch updates are essential for maintaining the security, stability, and performance of your Kubernetes clusters. This guide explains how servers.com simplifies the process of automating these updates.

A patch-version of a Kubernetes cluster can be updated automatically within a time slot of your choice.

The deployment process

You will be notified about the coming upgrade by email. When a cluster is being upgraded, it will assume a ‘pending’ status and will become temporarily unavailable. Control plane nodes are upgraded one by one, and worker nodes are upgraded by groups with a maximum of 10 servers per group.

If a Kubernetes upgrade exceeds the maintenance window, it will be paused and the cluster will return to an ‘active’ status, becoming available again. The Kubernetes cluster version will remain the same. The upgrade will then resume in the next available time slot, changing to the ‘pending’ status again. The Kubernetes version will be changed only after the last worker node has been upgraded.

It is not possible to downgrade a Kubernetes cluster to a previous version.

Important! Do not delete servers.com SSH keys on worker nodes, as this will prevent the upgrade process from being executed.

Upgrade settings

To set up a preferable time slot, go to the Kubernetes cluster details page and click ‘edit’ near the upgrade settings field. There are four options of maintenance frequency:

• Disabled - a cluster won't be upgraded automatically. Upgrade skipping is at your own risk.

• Anytime - an upgrade can be started anytime.

• On selected days - an upgrade will be done on a selected day of the week at the specified time.

• Daily - an upgrade will be done at the specified time of any day.

Automating Kubernetes patch updates with servers.com ensures your clusters remain secure and high-performing, while offering flexibility to match your operational needs.

Suggested Articles