Upgrading a Cluster

Geeper automatically checks for new Kubernetes releases and tells you when your cluster can be upgraded. You don’t need to track release notes or plan the rollout — just click when you’re ready.

When an upgrade is available

A banner appears on the cluster overview page showing the available version. Upgrades are offered one step at a time:

• Patch update — e.g. 1.31.4 → 1.31.5. Safe to apply at any time.
• Minor update — e.g. 1.31.x → 1.32.x. Offered once all patches for the current minor are applied.

Geeper follows Kubernetes Version Skew Policy and never skips minor versions, which keeps the upgrade path safe and supported.

Running an upgrade

1. Open your cluster
2. Click Upgrade in the banner showing the available version
3. Geeper takes it from there:
   • The control plane updates first
   • Once the control plane is ready, all worker nodes roll over automatically
4. The cluster stays in Upgrading status until all nodes are done, then returns to Running

What to expect

Workloads keep running during the upgrade. The control plane briefly restarts, and worker nodes are updated one by one. For single-node clusters there may be a short interruption.

Stuck or failed upgrade

If the upgrade fails, the cluster status switches to Error with a message explaining what happened. You can retry by triggering the upgrade again from the cluster page.