Kubernetes Release 1.27 Countdown
Swapnil K.
Helping Customer teams with Cloud Native Ops, Platform Engg, Solutions for Observability needs | Experience with Security, Compliance, Automation | Aspiring Fractional Exec
As we approach close to the Kubernetes 1.27 release, it is very exciting to see the enhancements this release brings to the best container orchestration engine. I am taking this opportunity to revive the newsletter and post some articles discussing the highlights, features that have been introduced for the first time in the release, those that are matured and the ones which are deprecated.
This is the landing page for the set of articles with deep-dives into release enhancements.
The highlight of Kubernetes release 1.27 is actually something the platform heavily relies on but is essentially outside of the platform. Yes, you got it right, it is Freeze `k8s.gcr.io` image registry change. The effort to move away from k8s.gcr.io , which was hosted in Google Cloud was thought few releases earlier and from release 1.24 onwards the patch releases are not released to this registry. From release 1.25 onwards, the default image registry has been set to registry.k8s.io and has been updated in all relevant tools like kubeadm, kubelet.
The old registry k8s.gcr.io will be frozen on April, 03, 2023 and an announcement has been made k8s.gcr.io Image Registry Will Be Frozen From the 3rd of April 2023 | Kubernetes. This adds additional feather to Kubernetes ecosystem making one of its core component truly multi-cloud and will be closer to your datacenter, “no matter” what cloud provider you use.
More release updates to follow...
More updates to subscribe to the Cloud Native Hero! Newsletter for updates in 2023.