Oracle Cloud Infrastructure Kubernetes Engine (OKE) now supports rolling back a node pool to an earlier Kubernetes version, helping simplify recovery when issues occur after an upgrade.
Before this release, recovery required creating a replacement node pool, migrating workloads, draining the old nodes, and deleting the original node pool. Customers can now select an earlier supported version for the existing node pool and then cycle or replace its worker nodes.
A node pool can be rolled back to any supported version that remains within the allowed version-skew range of the cluster. Eligible rollback versions appear in the OCI Console and are also available through the CLI, SDKs, and APIs.
How to roll back a node pool
- Open the OKE cluster in the OCI Console.
- Select Node Pools, then choose the node pool you want to update.
- Click Edit and select an eligible earlier Kubernetes version.
- Save the change and complete the standard node cycling or replacement process to move the worker nodes to the selected version.
- Verify that the node pool and worker nodes are running the expected Kubernetes version.
This release does not support rolling back the Kubernetes version of the cluster itself.
Useful links
Node Pool Kubernetes Version Rollback docs