Upgrade a workload cluster's Kubernetes version
Upgrade an NVIDIA Kubernetes Engine (NVKE) workload cluster’s control plane, then each worker node pool, within the Kubernetes version skew policy. The API rejects a pool version with a newer minor or major version than the control plane, and any pool version change while the control plane upgrades.
Before you begin
- The cluster meets the upgrade rows of Supported platforms and versions.
Upgrade the control plane
-
Let NVKE replace control-plane nodes, adding each new node before it removes an old one.
A control plane with one node needs
maxSurge: 1: NVKE removes a control-plane node only while at least two are healthy. -
Set the target version.
Send one version change. Until
STATUSshowsUpgrading, a second one is checked against the new target, not the running version, and replaces it. -
Wait until
STATUSinnvkectl get clusters <WORKLOAD_CLUSTER>isProvisionedagain and every control-plane node showsv<K8S_VERSION>inkubectl --kubeconfig <WORKLOAD_CLUSTER>.kubeconfig get nodes, with the kubeconfig from Get the admin kubeconfig.
Warning: On a control plane with one node, the Kubernetes API can be unavailable briefly at the end of the upgrade, while kubeadm upgrades the add-ons.
Upgrade a worker node pool
<API_URL> and the API token are described in Manage node pools. Upgrade the control plane first: the API rejects a pool version with a newer minor or major version than the control plane. An older version is accepted, so the same request rolls a pool back.
-
Set the pool’s version, and let NVKE add one new node. With
maxSurge: 0, the default, the change adds no node. -
Replace the old nodes one at a time, as described in Control automatic node replacement. Delete an old node only after the new one is
Readyon the new version.