One-year support window
Starting with 1.19, each minor release receives patch support for one year instead of nine months, based on survey data about how slowly users upgrade.
Kubernetes minor release · “Accentuate the Paw-sitive”
A 20-week cycle, stretched by the events of 2020, that lengthened each minor version's support window to one year and brought Ingress to GA, structured logging, and new storage-awareness features.
End of life since 28 Oct 2021 (5.0 years ago). No more patches upstream.
Starting with 1.19, each minor release receives patch support for one year instead of nine months, based on survey data about how slowly users upgrade.
After a long beta that made it a de facto standard, Ingress becomes a v1 API that the project commits to support.
The kubelet's automatic renewal of its client certificate and key as expiry approaches graduates to stable.
klog gains structured methods such as InfoS and ErrorS that take a message plus key-value pairs, making control-plane logs easier to parse.
CSI drivers can report remaining capacity, which the scheduler uses when choosing a node so pods are not placed where storage would run out.
Any dynamically provisioning storage driver can supply a volume whose lifetime is tied to the Pod, with full StorageClass and PVC features.
Summarised in our own words from the official “Kubernetes 1.19: Accentuate the Paw-sitive” announcement (34 tracked enhancements), © The Kubernetes Authors, CC BY 4.0.
No API versions were removed in 1.19.
Still served in 1.19, but the API server answers with a deprecation warning and a removal is scheduled.
AdmissionReview admission.k8s.io/v1LocalSubjectAccessReview authorization.k8s.io/v1SelfSubjectAccessReview authorization.k8s.io/v1SelfSubjectRulesReview authorization.k8s.io/v1CertificateSigningRequest certificates.k8s.io/v1Event events.k8s.io/v1Ingress networking.k8s.io/v1IngressClass networking.k8s.io/v1
From the official version skew policy as it stands today.
The API server must not skip minor versions.