Support for Kubernetes version 1.37.1

OCI Kubernetes Engine (OKE) now supports Kubernetes version 1.37.1, in addition to versions 1.36.4 and 1.35.2. With the availability of support for Kubernetes version 1.37.1, OKE will cease support for Kubernetes version 1.34.10 on December 21, 2026. Oracle strongly recommends you immediately upgrade clusters to Kubernetes version 1.35.2, 1.36.4, or 1.37.1. For more information about Kubernetes version 1.37.1, see the Kubernetes Changelog.

Note the following:

  • Although Kubernetes version 1.34.10 will not be supported after December 21, 2026, it might continue to be available for selection. However, Oracle strongly recommends you upgrade clusters to Kubernetes version 1.35.2, 1.36.4, or 1.37.1.
  • New clusters that you create with OKE to run Kubernetes version 1.36.1 or later use Kubernetes Key Management Service (KMS) provider version 2 for Kubernetes secret objects from the time the cluster is created.

    When you upgrade an existing cluster that uses a master encryption key you manage to Kubernetes version 1.36.1 or later, OKE starts using KMS provider version 2 for new Kubernetes secret objects and for existing secret objects that are subsequently updated. Existing unchanged secret objects can remain encrypted using KMS provider version 1. OKE retains KMS provider version 1 as a read fallback and does not automatically migrate all existing secret objects.

    To re-encrypt all existing unchanged Kubernetes secret objects using KMS provider version 2, see Migrating Kubernetes Secrets to KMS v2.

  • For worker nodes in clusters running Kubernetes version 1.35 (and later), Kubernetes Engine supports OKE OL8 images, and custom images based on OKE OL8 images. Custom images based on OL8 platform images are also supported, but only if you enable cgroups v2 (see Enabling Cgroups v2 on OL8 Worker Nodes Using Custom Images).

    In clusters running Kubernetes version 1.35 (and later), the use of platform images (both OL7 platform images and OL8 platform images) is not recommended. We strongly recommend the use of OKE images for all new deployments and upgrades. If you want to continue to use a platform image, create a custom image based on the platform image and specify the custom image's OCID when creating or updating a node pool (note that we do not recommend this approach).

    For more information, see Notes about Kubernetes version 1.35 (and later) and Support for OKE Images, Platform Images, and Custom Images.

  • From Kubernetes version 1.37 onward, by default Kubernetes Engine provisions a Kubernetes service of type LoadBalancer as a flexible load balancer, with a minimum bandwidth and maximum bandwidth of 100Mbps. Existing load balancers are not converted or resized, and explicit shape annotations continue to take precedence. For more information, see Defining Kubernetes Services of Type LoadBalancer.
  • From Kubernetes version 1.37 onward, TLS secrets referenced by a Kubernetes service of type LoadBalancer must be in the same namespace as the service. Earlier supported Kubernetes releases warn about cross-namespace TLS secret references, but Kubernetes version 1.37 enforces this restriction.

    This restriction applies to the following Kubernetes Engine annotations:

    • service.beta.kubernetes.io/oci-load-balancer-tls-secret
    • service.beta.kubernetes.io/oci-load-balancer-tls-backendset-secret

    You can specify a secret as either <secret-name> or <service-namespace>/<secret-name>. From Kubernetes version 1.37 onward, if you specify a different namespace, Kubernetes Engine rejects the configuration before reading the secret, and the service is not reconciled until the reference is corrected. Therefore, before upgrading clusters to Kubernetes version 1.37, identify services of type LoadBalancer that use annotations to refer to TLS secrets in a different namespace. Copy each secret into the corresponding service namespace and update the annotation.

To upgrade a cluster to a new Kubernetes minor version:

  1. Upgrade the Kubernetes version running on the control plane by following the instructions in Upgrading the Kubernetes Version on Control Plane Nodes in a Cluster.
  2. Having upgraded the control plane, upgrade the Kubernetes version running on worker nodes in a node pool by following the instructions in Upgrading the Kubernetes Version on Worker Nodes in a Cluster.

Note:

Always follow the Kubernetes skew policy for Kubernetes minor version support. Note that in Kubernetes version 1.28, the Kubernetes skew policy 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. From Kubernetes version 1.28, the Kubernetes skew policy allows control plane nodes to be up to three versions ahead of worker nodes.

Example skew policy:

  • Kubernetes control plane nodes are at version 1.37.1
  • Kubernetes worker nodes must be at version 1.37.1, 1.36.4, 1.35.2, or 1.34.10

For more information, see Upgrading Clusters to Newer Kubernetes Versions.

Skipping versions when upgrading

Kubernetes requires that you upgrade control plane nodes one minor version at a time. However, you don't have to upgrade worker nodes one minor version at a time.