Update 2023-05-04: All clusters have been upgraded to
We are starting to roll out AKS and EKS 1.25. This brings our supported AKS platforms to
v1.25.5 and EKS to
v1.25.6. This release includes the removal of several deprecated API Version, so please make sure to check Actions to take! Please also make sure to update to our recommended client versions mathcing this upgrade
- Publish of this changelog
- We start rollout of non-production cluster over the course of the following days
- If we have detected (possible) use of older apiVersion in your environments, we will post a GitHub issue in your repository with the details
- Production rollouts are planned to start during the week of 10/04
- Update this changelog when everything is finished
Important changes between K8s 1.24 and 1.25
Here’s a small list of some major themes:
- Ephemeral Containers, useful for debugging, are now stable
- Container registry moves from
redirects to , and it will evetually be completely removed, [see the announcement for more info](https://kubernetes.io/blog/2023/03/10/image-registry-redirect/)
- We have updated our remaining references to
- PodSecurityPolicy (PSP) is removed, replaced by Pod Security Admission (PSA)
- PSPs have already been deprecated since K8s 1.21 and the API is now fully removed. It has been replaced by Pod Security Admission (PSA)
AKS specific changes
Azure AKS 1.25 GA release notes: https://github.com/Azure/AKS/releases/tag/2022-12-04.
EKS specific changes
AWS EKS 1.25 release notes: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-1.25.
In the process of upgrading EKS the following components have also been upgraded:
- KubeProxy to
- Cluster Autoscaler to
- Metrics Server to
Actions to take
This release removes support for several deprecated API versions!
Most notable the following:
Others, which or unlikely to impact you:
policy/v1beta1has been removed!
All existing resources deployed to the Kubernetes clusters upgraded to v1.25 will keep on working, internal resources deployed via older apiVersions will automatically migrate. However the Kubernetes API will stop accepting manifests using these removed apiVersions. Concretely this means that if your manifests, helm charts, … are not updated, you will not be able to deploy new changes.
Please make sure to update your workloads accordingly to prevent development disruption. We will also post a GitHub issue in your repository if we have detected such use of older versions.