Kubernetes Version Policy
A KKP minor version supports all Kubernetes versions which were supported upstream
at the time of its release. You can find more details about the upstream support
policy in the Version Skew Policy.
As time passes, patch versions of KKP will support new patch versions of Kubernetes
that have been released since, as well as drop old patch versions if they are
affected by critical bugs.
KKP will typically drop support of minor versions of Kubernetes which have gone EOL.
One notable exception is when upgrading from an older version of Kubernetes might
require extensive migration of loads running within the updated clusters (e.g. API
version deprecations) – in these cases KKP will maintain LIMITED support of an EOL
Kubernetes version(s) for an additional release cycle for the purpose of facilitating
these migrations.
Supported Kubernetes Versions
In the following table you can find the supported Kubernetes versions for the
current KKP version.
KKP version | 1.31 | 1.30 | 1.29 | 1.28 | 1.27 | 1.26 |
---|
2.26.x | ✓ | ✓ | ✓ | ✓ | – | – |
2.25.x | – | – | ✓ | ✓ | ✓ | – |
2.24.x | – | – | – | ✓ | ✓ | ✓ |
Upgrades from a previous Kubernetes version are generally supported whenever a version is
marked as supported, for example KKP 2.26 supports updating clusters from Kubernetes 1.30 to 1.31.
Provider Incompatibilities
KKP may have incompatibilities with cloud providers, e.g. because their in-tree cloud provider
implementation has been removed from upstream Kubernetes. For KKP 2.26.x, no provider incompatibilities exist.