Update 2023-09-28: All clusters have been upgraded to v1.27.
We are rolling out AKS and EKS v1.27. This brings our supported AKS platforms to v1.27.3 and EKS to v1.27(.4). Please make sure to update to our recommended client versions matching this upgrade
Timeline:
- Testing & rollout to non-production clusters
- Publish of this changelog
- 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 course of weeks of 25/09 & 2/10
- Update this changelog when everything is finished
Important changes between K8s 1.26 and 1.27
For more detailed info on what’s new and changed, please make sure to check the Kubernetes 1.27 release announcement and the full Kubernetes 1.27.x changelog.
This release mostly focusses on graduating many features/apis to alpha, beta and stable status. Here’s a small list of the most relevant changes:
AKS specific changes
Azure AKS 1.27 GA release notes.
EKS specific changes
AWS EKS 1.27 announcement blog and release notes.
In the process of upgrading EKS the following components have also been upgraded:
- KubeProxy to
v1.27.4-eksbuild.2 - CoreDNS to
v1.10.1-eksbuild.4 - VPC CNI to
v1.14.1-eksbuild.1 - EBS CSI Driver to
v1.22.0-eksbuild.2 - Cluster Autoscaler to
v1.27.3
The new VPC CNI comes with new NetworkPolicies support! This means that customers can now implement both Pod networking and network policies to secure the traffic in their Kubernetes clusters, whitout the need of deploying any extra component.
Up until now, we’ve been supporting Calico as an optional feature for our managed Kubernetes platforms, not as a full-blown CNI, but only as a NetworkPolicies engine. Calico is quite resource-intensive, since it requires several components to function correctly, so thanks to this update we’ll be able to completely remove Calico and all its components and instead rely on the VPC CNI for NetworkPolicies support. In the coming weeks we’ll be enabling by default the NetworkPolicies support on the CNI for all clusters, and removing Calico from the clusters that had it enabled. This shouldn’t have any impact on customer workloads or service availability.
Actions to take
There are no actions to take for you this release.