Upgrade hop
Kubernetes 1.29 → 1.30
1.30 is itself end of life. If you are on 1.29 today, plan the whole path to a supported version (at least 1.35) with the upgrade planner.
1 · Fix removed APIs first
No API versions are removed between 1.29 and 1.30.
2 · Other changes that can bite
Removed in 1.30
- The SecurityContextDeny admission plugin, deprecated since 1.27, was removed; Pod Security Admission is the recommended replacement.
Our summary of the 1.30 release announcement (CC BY 4.0). Read the full changelog for your components.
3 · Upgrade in this order
- Prepare. Move every node to 1.27 or newer if any are older: a 1.30 API server supports kubelets back to 1.27 only. Upgrade to the newest 1.29 patch,
1.29.15. - kube-apiserver to 1.30 (in HA clusters, one instance at a time; old and new may differ by one minor during the roll). Use the newest patch,
1.30.14. - kube-controller-manager, kube-scheduler, cloud-controller-manager to 1.30, once every API server is on 1.30.
- kubelet on each node (drain first). Optional in this hop: kubelets from 1.27 to 1.30 all work with a 1.30 control plane.
- kube-proxy: no newer than the API server, and within the same window as the kubelet it runs beside.
- kubectl: 1.29 to 1.31 all talk to a 1.30 API server.
From the official version skew policy. Managed services run the control-plane steps for you; node pools are still yours to schedule.