Supported Versions of Kubernetes
Find out about the Kubernetes versions that Kubernetes Engine (OKE) currently supports, along with details of previously supported versions and planned support for future versions.
When Kubernetes Engine support for a new version of Kubernetes is announced, an older Kubernetes version will subsequently cease to be supported. Oracle recommends that you upgrade existing clusters to use the most recent Kubernetes version that Kubernetes Engine supports.
This topic lists:
Currently Supported Kubernetes Versions
Kubernetes Engine supports three versions of Kubernetes for new clusters. For a minimum of 30 days after the announcement of support for a new Kubernetes version, Kubernetes Engine continues to support the fourth oldest available Kubernetes version. After that time, the older Kubernetes version ceases to be supported.
When creating a new cluster with Kubernetes Engine, Oracle recommends that you use the most recent Kubernetes version that Kubernetes Engine supports. When Oracle announces Kubernetes Engine support for a new Kubernetes version, Oracle recommends you upgrade existing clusters to use that new Kubernetes version as soon as possible.
Release Calendar
Kubernetes Engine (OKE) supports the following versions of Kubernetes for new clusters:
| Kubernetes Minor Version | Kubernetes Patch Version Supported by OKE | Upstream Minor Version Release Date | Upstream Minor Version End-of-life date | OKE Release Date | OKE End-of-life Date |
|---|---|---|---|---|---|
| 1.30 | 1.30.1 | 2024-04-17 | 2025-06-28 | 2024-07-23 | 30 days after 1.33 OKE Release Date (planned) |
| 1.29 | 1.29.1 | 2023-12-13 | 2025-02-28 | 2024-03-28 | 30 days after 1.32 OKE Release Date (planned) |
| 1.28 | 1.28.10 | 2023-08-15 | 2024-10-28 | 2024-09-03 | 30 days after 1.31 OKE Release Date (planned) |
| 1.28 | 1.28.2 | 2023-08-15 | 2024-10-28 | 2023-12-19 | 2024-10-08 |
Legal Disclaimer: The table is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracle's products may change and remains at the sole discretion of Oracle Corporation.
Notes about Kubernetes Engine Support for Kubernetes Version 1.30
Note that Kubernetes Engine support for Kubernetes version 1.30 also introduces changes to default Kubernetes Engine behavior with regards CPU and memory reservation. On clusters running Kubernetes version 1.30 and later, CPU and memory resources for managed nodes are reserved by default, using the --kube-reserved and --system-reserved kubelet flags respectively (as recommended in Best Practice: Reserve resources for Kubernetes and OS system daemons). As a result, on clusters running Kubernetes version 1.30 and later, there is a difference between a node's total resources, and the resources that are available for workloads to request. For more information, see Best Practice: Reserve resources for Kubernetes and OS system daemons.
Notes about Kubernetes Engine Support for Kubernetes Version 1.28
Note that in Kubernetes version 1.28, the Kubernetes skew policy has expanded. Prior to Kubernetes version 1.28, the skew policy required a cluster's control plane nodes to be no more than two versions ahead of worker nodes. Starting from Kubernetes version 1.28, the Kubernetes skew policy allows control plane nodes to be up to three versions ahead of worker nodes. See the Kubernetes version skew support policy.
Kubernetes Engine applies the expanded skew policy to clusters running Kubernetes version 1.28 and later.
Notes about Kubernetes Engine Support for Kubernetes Version 1.27
Note that Kubernetes version 1.27 stopped serving the following deprecated Kubernetes API:
- CSIStorageCapacity (storage.k8s.io/v1beta1 API version)
For more information about migrating from the deprecated APIs, see the Kubernetes Deprecated API Migration Guide.
Notes about Kubernetes Engine Support for Kubernetes Version 1.26
Note that Kubernetes version 1.26 stopped serving a number of deprecated Kubernetes APIs, including:
- FlowSchema (flowcontrol.apiserver.k8s.io/v1beta1 API version)
- HorizontalPodAutoscaler (autoscaling/v2beta2 API version)
- PriorityLevelConfiguration (flowcontrol.apiserver.k8s.io/v1beta1 API version)
For more information about migrating from the deprecated APIs, see the Kubernetes Deprecated API Migration Guide.
Support for Kubernetes version 1.26.7 was released to address the following upstream issues with Kubernetes version 1.26.2:
- https://github.com/opencontainers/runc/issues/3849: A bug in kubelet causes a memory leak on nodes using cgroup v1 on the 5.15 Linux kernel. Oracle Linux 8.7 images use the 5.15 Linux kernel, so Oracle Linux 8.7 images are impacted by the bug.
- https://github.com/cri-o/cri-o/issues/6805: Metrics are missing after a crio restart.
Notes about Kubernetes Engine Support for Kubernetes Version 1.25
Note that Kubernetes version 1.25 stopped serving a number of deprecated Kubernetes APIs, including:
- CronJob (batch/v1beta1 API version)
- EndpointSlice (discovery.k8s.io/v1beta1 API version)
- Event (events.k8s.io/v1beta1 API version)
- HorizontalPodAutoscaler (autoscaling/v2beta1 API version)
- PodDisruptionBudget (policy/v1beta1 API version)
- PodSecurityPolicy (policy/v1beta1 API version)
- RuntimeClass (node.k8s.io/v1beta1 API version)
For more information about migrating from the deprecated APIs, see the Kubernetes Deprecated API Migration Guide.
Support for Kubernetes version 1.25.12 was released to address the following upstream issues with Kubernetes version 1.25.4:
- https://github.com/opencontainers/runc/issues/3849: A bug in kubelet causes a memory leak on nodes using cgroup v1 on the 5.15 Linux kernel. Oracle Linux 8.7 images use the 5.15 Linux kernel, so Oracle Linux 8.7 images are impacted by the bug.
- https://github.com/cri-o/cri-o/issues/6805: Metrics are missing after a crio restart.
The upstream Kubernetes project deprecated pod security policies in Kubernetes version 1.21, and removed the feature in Kubernetes version 1.25. Consequently, Kubernetes Engine does not support pod security policies and the PodSecurityPolicy admission controller in clusters running Kubernetes version 1.25 and later.
If you require similar functionality, consider using Kubernetes pod security standards and the PodSecurity admission controller instead (along with the Privileged, Baseline, and Restricted policies). By default, Kubernetes Engine enables the PodSecurity admission controller in clusters running Kubernetes version 1.23 and later, in order to support pod security standards. For more information about Kubernetes pod security standards, and the PodSecurity admission controller, see Pod Security Standards in the Kubernetes documentation.
Alternatively, consider using other alternatives that are being developed in the Kubernetes ecosystem to enforce policies.
If you do decide to move from using pod security policies and the PodSecurityPolicy admission controller to using pod security standards and the PodSecurity admission controller, see Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller in the Kubernetes documentation. Note that it is important to complete the migration before creating a new cluster running Kubernetes version 1.25, or before upgrading an existing Kubernetes version 1.24 cluster to run Kubernetes version 1.25. Also note that the Console provides a convenient way to disable the use of the PodSecurityPolicy admission controller in existing Kubernetes clusters created and managed by Kubernetes Engine (see Using the Console to Disable the PodSecurityPolicy Admission Controller).
Notes about Kubernetes Engine Support for Kubernetes Version 1.22
Note that Kubernetes version 1.22 stopped serving a number of deprecated Kubernetes APIs, including:
- Webhook resources
- CustomResourceDefinition
- APIService
- TokenReview
- SubjectAccessReview resources
- CertificateSigningRequest
- Lease
- Ingress
- IngressClass
- RBAC resources
- PriorityClass
- Storage resources
For more information about migrating from the deprecated APIs, see the Kubernetes Deprecated API Migration Guide.
Planned Support for Future Kubernetes Versions
Kubernetes Engine support is currently planned for the following future versions of Kubernetes. Note that future dates are subject to change without notice. In addition, note the Legal Disclaimer following the table.
| Kubernetes Minor Version | Kubernetes Patch Version Supported by OKE | Upstream Minor Version Release Date | Upstream Minor Version End-of-life date | OKE Release Date |
|---|---|---|---|---|
| 1.31 | To Be Confirmed | 2024-08-13 | To Be Confirmed | November 2024 (planned) |
| 1.32 | To Be Confirmed | 2024-12-18 | To Be Confirmed | March 2025 (planned) |
| 1.33 | To Be Confirmed | April 2025 | To Be Confirmed | To Be Confirmed |
Legal Disclaimer: The table is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracle's products may change and remains at the sole discretion of Oracle Corporation.
Previously Supported Kubernetes Versions
Kubernetes Engine previously supported the following versions of Kubernetes:
| Kubernetes Version | Support Ended |
|---|---|
| 1.27.10 | August 27, 2024 |
| 1.27.2 | May 21, 2024 |
| 1.26.7 | April 29, 2024 |
| 1.26.2 | October 13, 2023 |
| 1.25.12 | February 15, 2024 |
| 1.25.4 | October 13, 2023 |
| 1.24.1 | September 26, 2023 |
| 1.23.4 | June 22, 2023 |
| 1.22.5 | February 22, 2023 |
| 1.21.5 | October 13, 2022 |
| 1.20.11 | July 19, 2022 |
| 1.20.8 | November 7, 2021 |
| 1.19.15 | April 22, 2022 |
| 1.19.12 | November 7, 2021 |
| 1.19.7 | August 13, 2021 |
| 1.18.10 | February 9, 2022 |
| 1.17.13 | September 8, 2021 |
| 1.17.9 | April 17, 2021 |
| 1.16.15 | April 17, 2021 |
| 1.15.12 | February 2, 2021 |
| 1.15.7 | February 2, 2021 |
| 1.14.8 | December 15, 2020 |
| 1.13.x | March 21, 2020 |
| 1.12.7 | January 29, 2020 |
| 1.12.6 | April 15, 2019 |
| 1.11.9 | September 9, 2019 |
| 1.11.8 | April 15, 2019 |
| 1.11.x versions prior to 1.11.8 | March 13, 2019 |
| 1.10.x | April 12, 2019 |
| 1.9.x | December 11, 2019 |
| 1.8.x | September 7, 2018 |
Notes about Kubernetes Engine Support for Kubernetes Version 1.20
With the announcement of support for Kubernetes version 1.20.8, the container runtime used by Kubernetes Engine changes from Docker to CRI-O. However, you don't have to change any of your existing Docker images because Docker images are Open Container Initiative (OCI) compliant. As far as Kubernetes is concerned, all OCI-compliant images look the same.
Note the following:
- CRI-O is an implementation of the Kubernetes Container Runtime Interface (CRI), which enables the use of OCI-compatible runtimes. CRI-O can pull your existing Docker images and run them on your Kubernetes version 1.20.8 clusters.
- When using the Docker runtime, the default configuration captures the standard output and standard error streams of containers using the JSON format. In contrast, CRI-O uses the Logrus format. If you use a logging tool such as Fluentd or Fluent Bit, update the tool's configuration to use a new parser to parse CRI logs. For example:
- If you use Fluentd, use the fluent-plugin-parser-cri parser.
- If you use Fluent Bit, use the Container Runtime Interface (CRI) parser.
- You might have a workflow in a cluster that relies on the underlying docker socket /var/run/docker.sock (a pattern often referred to as Docker in Docker). Starting with Kubernetes version 1.20.8, such a workflow no longer functions.
- If you previously used the Docker CLI to run commands on a host, you have to use crictl (a CLI for CRI-compatible container runtimes) instead.
- The upstream Kubernetes project is deprecating Docker as a container runtime after Kubernetes version 1.20.
To find out more:
- See the Kubernetes 1.20.8 Changelog for more information about Kubernetes 1.20.8
- See the Dockershim Deprecation FAQ for more information about the deprecation of the dockershim adapter (which previously enabled the kubelet to interact with Docker as if Docker were a CRI-compatible runtime)