k8s.gcr.io frozen
No new images go to k8s.gcr.io; 1.27 is only on registry.k8s.io, and older-branch patch releases stopped going there after April. Consider running a local mirror.
Kubernetes minor release · “Chill Vibes”
A large, calm release that froze the old k8s.gcr.io registry and made seccomp defaulting stable. It also cleaned out many feature gates and flags for features that had already gone GA.
End of life since 16 Jul 2024 (2.3 years ago). No more patches upstream.
No new images go to k8s.gcr.io; 1.27 is only on registry.k8s.io, and older-branch patch releases stopped going there after April. Consider running a local mirror.
Start the kubelet with --seccomp-default and pods get the runtime's RuntimeDefault seccomp profile instead of running unconfined.
Pods can carry schedulingGates so the scheduler ignores them until the gates are removed, avoiding needless scheduling churn.
Admins can read service logs from nodes through the API when the NodeLogQuery gate and two kubelet settings are enabled.
Volumes can be limited to a single pod; the beta adds scheduler preemption for pods using such claims.
Volumes can be mounted with the right SELinux context at once rather than relabeling every file, for ReadWriteOncePod volumes with supporting CSI drivers.
Summarised in our own words from the official “Kubernetes v1.27: Chill Vibes” announcement (60 tracked enhancements), © The Kubernetes Authors, CC BY 4.0.
Upgrading to 1.27 breaks any manifest, Helm chart or client that still uses these API versions. Move them to the version in the last column before you upgrade the control plane.
| Kind | API version | Stops being served | Use instead |
|---|---|---|---|
| CSIStorageCapacity | storage.k8s.io/v1beta1 | 1.27 | storage.k8s.io/v1 |
From the release announcement; our wording.
From the official version skew policy as it stands today.
The API server must not skip minor versions.