What’s New in Kubernetes 1.19? A Deep Dive into Year‑Long Support and Key Features

Release Overview

Kubernetes 1.19 marks the second release of 2020 and the longest release cycle to date, lasting 20 weeks. It bundles 33 enhancements, of which 12 have reached stable, 18 are in beta, and 13 remain in alpha.

Extended Support Window

A 2019 LTS survey showed many users could not upgrade within the previous nine‑month support period. Extending support to 12‑14 months would enable roughly 30% more users to stay current. Consequently, starting with 1.19 the support window is extended to a full year, providing a buffer that aligns with typical annual planning cycles.

Storage Capacity Tracking

The new alpha feature adds an API for CSI drivers to report available storage capacity. The scheduler can then consider this information when placing pods, laying the groundwork for dynamic resource allocation for local volumes and other capacity‑constrained storage types.

Generic Ephemeral Volumes

An alpha feature allows any CSI driver that supports dynamic provisioning to provide temporary volumes whose lifecycle is bound to a pod. This enables use cases such as temporary storage on persistent memory or a node‑local disk, while retaining full support for all StorageClass parameters and existing PVC features like snapshots and resizing.

CSI Volume Health Monitoring

Kubernetes 1.19 ships an alpha version of CSI health monitoring. CSI drivers can report abnormal volume conditions to the control plane, which are then surfaced as events on PVCs or Pods, forming the basis for programmatic detection and remediation of single‑volume health issues.

Ingress GA

Although the Ingress API has been in beta for a long time, widespread adoption by users and Ingress controller vendors has effectively granted it de‑facto GA status. The current API is declared community‑supported V1, while work continues on a V2 API with an expanded feature set.

Structured Logging

Prior to v1.19, control‑plane logs lacked a consistent structure, making parsing and analysis difficult and often requiring ad‑hoc regex solutions. The new approach introduces a structured logging interface that pairs each existing formatted method (Infof, Errorf) with a structured counterpart (InfoS, ErrorS) accepting a message and a list of key‑value pairs, enabling gradual adoption of structured logs.

New klog Methods

Kubernetes 1.19 adds new klog methods that provide a more structured way to log messages. The new methods (InfoS, ErrorS, etc.) take the log message as the first argument and a variadic list of key‑value pairs as the second, allowing incremental migration without breaking existing code.

Kubelet Client TLS Certificate Rotation

Kubelet authenticates to the API server using a client certificate. Since v1.8 a beta process existed for obtaining an initial certificate and rotating it on expiry. In v1.19 this mechanism graduates to stable, automatically handling certificate discovery, generation of CSRs, and renewal, greatly improving cluster manageability.

Other Updates

Stable features introduced in 1.19 include:

Seccomp

Kubelet client TLS certificate rotation

Node‑restricted API access

Redesigned Event API

Ingress V1

CertificateSigningRequest API

Docker‑less Kubelet builds

Major changes:

Node Topology Manager

New Endpoint API

One‑year support window

Other important features:

Multiple scheduling profiles

Immutable Secrets and ConfigMaps