Version information
Kubernetes version and support period
Kubernetes version lifecycle
The Kubernetes open-source software (OSS) community releases minor versions three times a year, with a release cycle of approximately 15 weeks. A released minor version goes through a support period of about 14 months (12 months of standard patches, 2 months of maintenance) before reaching EOL (End of Life).
For the Kubernetes release and EOL dates, as well as the support period, please refer to the following link.
Samsung Cloud Platform Kubernetes Engine (SKE) Version Release Plan
SKE validates and delivers the stable patch versions among the released OSS minor versions. Therefore, the release timing of the version provided by SKE differs from that of the same OSS version.
Additionally, for previously released versions, taking into account the open‑source EOL schedule, technical support will be phased out sequentially starting with the older versions (End of Tech support, EoTS).
The release schedule and end-of-life schedule for OSS and SKE are as follows.
| Version | OSS release | OSS EOL | SKE release | SKE EoTS |
|---|---|---|---|---|
| v1.29 (EoTs) | 2023-12-13 | 2025-02-28 | 2024-10 | 2026-03-31 |
| v1.30 (EoTs) | 2024-04-17 | 2025-06-28 | 2025-02 | 2026-06-30 |
| v1.31 | 2024-08-13 | 2025-10-28 | 2025-07 | 2026-10-28 |
| v1.32 | 2024-12-11 | 2026-02-28 | 2025-10 | 2027-02-28 |
| v1.33 | 2025-04-23 | 2026-06-28 | 2025-12 | 2027-06-28 |
| v1.34 | 2025-08-27 | 2026-10-27 | 2026-03 | 2027-10-27 |
| v1.35 | 2025-12-17 | 2027-02-28 | 2026-07 | 2028-02-28 |
| v1.36 | 2026-04-22 | 2027-06-28 | 2026-09 | 2028-06-28 |
Feature limitation when technical support ends (EoTS)
If the Kubernetes version offered by SKE reaches end‑of‑technical‑support (EoTS) status, the features available in that version may be limited.
- Create new cluster → Creation not possible
- Existing cluster upgrade → upgrade possible (upgrade possible even if the newer version is EoTS)
- Create node pool in existing cluster → creation possible
- Since EOL versions may have vulnerabilities, we recommend upgrading to a newer version.
- You can upgrade the control plane and node pools from the Samsung Cloud Platform Console, and no additional costs are incurred for the upgrade.
- For stable operation, perform compatibility testing of the upgrade version before proceeding with the upgrade.
OS and GPU drivers
The OS and GPU driver version information available for each K8s server type is as follows.
- The OS versions provided may vary by K8s version.
- When using GPU nodes, the related K8s components (nvidia-device-plugin, dcgm-exporter) are provisioned by default in the cluster.
- When deploying the gpu-operator, conflicts may occur due to duplicate component configurations. * Distribution and use are recommended, excluding the default components.
- When using an NPU node, no separate K8S component is provided. * If needed, please configure using the official Helm Chart.
- For end-of-life operating systems, you can create a node pool, but we recommend using the latest OS version.
| k8s version | Standard and High Capacity | GPU/NPU |
|---|---|---|
| v1.29 |
|
|
| v1.30 |
|
|
| v1.31 |
|
|
| v1.32 |
|
|
| v1.33 |
|
|
| v1.34 |
|
|
| v1.35 |
|
|
| v1.36 |
|
|
The OS versions and supported GPU/NPU server models for each GPU/NPU driver version are as follows.
- When creating a GPU node with the GPU-B300-3 server type, you must use an image with GPU driver version 580.126.20.
| GPU driver version | OS version | Supported model (server type) |
|---|---|---|
| ND 535.183.06 | Ubuntu 22.04 |
|
| ND 570.195.03 | Ubuntu 24.04 |
|
| ND 580.126.20 | Ubuntu 24.04 |
|
| FRD 2026.2.0 | Ubuntu 24.04 |
|