Kubernetes CSI Node Driver Registrar End of Life (EOL) Dates and End of Support (EOS) Dates
Kubernetes CSI Node Driver Registrar end of life (EOL) and end of support (EOS) dates: 19 Kubernetes CSI Node Driver Registrar versions have reached EOL, including Kubernetes CSI Node Driver Registrar 2.17 (EOL date: Sep 03, 2026) — no longer receiving security updates or patches. Kubernetes CSI Node Driver Registrar 2.18.0 is the current supported release. Also see Coder EOSL information for related end-of-life information.
Currently Supported Kubernetes CSI Node Driver Registrar Releases - Active EOS/EOSL Support (1)
| Release | Released | Support | Latest |
|---|---|---|---|
| 2.18 | (2 months ago) | Active | 2.18.0 (2 months ago) |
Kubernetes CSI Node Driver Registrar End of Life (EOL) Releases - No Longer Supported (19)
| Release | Released | Support | Latest |
|---|---|---|---|
| 2.17 | (6 months ago) | (2 months ago) | 2.17.0 (6 months ago) |
| 2.16 | (9 months ago) | (6 months ago) | 2.16.0 (9 months ago) |
| 2.15 | (1 year and 2 months ago) | (9 months ago) | 2.15.0 (1 year and 2 months ago) |
| 2.14 | (1 year and 5 months ago) | (1 year and 2 months ago) | 2.14.0 (1 year and 5 months ago) |
| 2.13 | (1 year and 11 months ago) | (1 year and 5 months ago) | 2.13.0 (1 year and 11 months ago) |
| 2.12 | (2 years and 2 months ago) | (1 year and 11 months ago) | 2.12.0 (2 years and 2 months ago) |
| 2.11 | (2 years and 5 months ago) | (2 years and 2 months ago) | 2.11.1 (2 years and 4 months ago) |
| 2.10 | (2 years and 10 months ago) | (2 years and 5 months ago) | 2.10.1 (2 years and 8 months ago) |
| 2.9 | (3 years and 2 months ago) | (2 years and 10 months ago) | 2.9.4 (2 years and 8 months ago) |
| 2.8 | (3 years and 6 months ago) | (3 years and 2 months ago) | 2.8.0 (3 years and 6 months ago) |
| 2.7 | (3 years and 10 months ago) | (3 years and 6 months ago) | 2.7.0 (3 years and 10 months ago) |
| 2.6 | (4 years and 1 month ago) | (3 years and 10 months ago) | 2.6.3 (3 years and 9 months ago) |
| 2.5 | (4 years and 9 months ago) | (4 years and 1 month ago) | 2.5.1 (4 years and 6 months ago) |
| 2.4 | (5 years ago) | (5 years ago) | 2.4.0 (5 years ago) |
| 2.3 | (5 years and 3 months ago) | (5 years ago) | 2.3.0 (5 years and 3 months ago) |
| 2.2 | (5 years and 6 months ago) | (5 years and 3 months ago) | 2.2.0 (5 years and 6 months ago) |
| 2.1 | (5 years and 11 months ago) | (5 years and 6 months ago) | 2.1.0 (5 years and 11 months ago) |
| 2.0 | (6 years and 2 months ago) | (5 years and 11 months ago) | 2.0.1 (6 years and 2 months ago) |
| 1.2 | (7 years and 2 months ago) | (6 years and 2 months ago) | 1.2.0 (7 years and 2 months ago) |
The Kubernetes CSI node driver registrar end of life picture is short: this sidecar container for the Container Storage Interface follows a "latest release only" policy, so each minor version loses maintenance once the next one ships. Below you will find every launch date, the versions your kubelet needs, and what to check on each node before you upgrade your CSI driver.
Kubernetes CSI Node Driver Registrar End of Life by Release
The node-driver-registrar publishes a new minor release every few months. The table shows the supported releases and the older ones whose maintenance has stopped. Today only 2.18 is inside its support window.
| Release | Released | Support ended | Container image |
|---|---|---|---|
| node-driver-registrar 2.18 | 3 Sep 2026 | Still supported | registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.18.0 |
| node-driver-registrar 2.17 | 21 May 2026 | Ended 3 Sep 2026 | registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.17.0 |
| node-driver-registrar 2.16 | 12 Feb 2026 | Ended 21 May 2026 | registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.16.0 |
| node-driver-registrar 2.15 | 12 Sep 2025 | Ended 12 Feb 2026 | v2.15.0 |
| node-driver-registrar 2.14 | 30 May 2025 | Ended 12 Sep 2025 | v2.14.0 |
| node-driver-registrar 2.13 | 19 Dec 2024 | Ended 30 May 2025 | v2.13.0 |
Supported versions
Only the latest release counts as supported. The Kubernetes CSI documentation lists the latest stable release branch plus a few older ones, but that page is not updated often, so trust the dates above.
Unsupported versions
Anything older than 2.18 is unmaintained. It keeps running, yet it gets no fixes, so plan your upgrade.
What the Registrar Sidecar Container Does for Your CSI Driver
The registrar registers your CSI driver with the kubelet through the kubelet plugin registration mechanism. The kubelet issues NodeGetInfo, NodeStageVolume and NodePublishVolume calls, and the registrar tells it which Unix domain socket to use. Each registrar talks to the driver over gRPC.
Required arguments
--csi-address: the path to the driver inside its pod, so the registrar can reach the CSI driver.--kubelet-registration-path: the driver socket path on the host node that the kubelet uses; it is not the registration socket.
Optional arguments
--http-endpoint: the address of a diagnostics server that reports whether the registrar has registered.--health-port: deprecated port for the older kubelet check server.
Required permissions
The registrar itself needs no cluster-wide access; it only needs the hostpath mount and permission to register itself on the node.
Compatibility and Deployment of the Registrar
Run the registrar as a sidecar in the driver's pod on every node, with one copy per node. The csi-node-driver-registrar image is built for CSI spec v1.5.0. The min k8s version is 1.13 and the recommended k8s version is 1.23.10. Mount the hostpath plugins_registry directory at /registration so the kubelet finds the registration socket. On Linux this works as described; on Windows you need Kubernetes 1.23.10, 1.24.4 or 1.25.0 or newer. Each version also has its own branch, such as release-2.13.
Health check with an exec probe
Besides the HTTP server, you can add an exec probe to the sidecar spec to confirm registration happened, which gives your health check a cheap liveness signal.
Security and Vulnerability Checks Before the Registrar Reaches End of Life
An unsupported registrar will not get a patched image, so scan it. Snyk's CVE-2024-24790 entry for a Chainguard build of version 2.7 was revoked as not affected, and its EPSS score was only 1.95%, a reminder to read a CVE report before you act. Docker Hardened Images ship the csi-node-driver-registrar with an SBOM, provenance and a FIPS variant, which helps compliance and supply chain reviews. The tool is written in Go (golang), and the Git repository on GitHub keeps a changelog of every fix.