Skip to content

Latest commit

 

History

History
91 lines (54 loc) · 4.6 KB

File metadata and controls

91 lines (54 loc) · 4.6 KB
copyright
years
2025, 2026
lastupdated 2026-03-31
keywords kubernetes, containers, 135, version 135, 135 update actions
subcollection containers

{{site.data.keyword.attribute-definition-list}}

1.35 version information and update actions

{: #cs_versions_135}

Review information about version 1.35 of {{site.data.keyword.containerlong}}. For more information about Kubernetes project version 1.35, see the Kubernetes change log{: external}. {: shortdesc}

This badge indicates Kubernetes version 1.35 certification for {{site.data.keyword.containerlong_notm}}{: caption="Kubernetes version 1.35 certification badge" caption-side="bottom"}

{{site.data.keyword.containerlong_notm}} is a Certified Kubernetes product for version 1.35 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

Release timeline

{: #release_timeline_135}

The following table includes the expected release timeline for version 1.35 of {{site.data.keyword.containerlong}}. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported. {: shortdesc}

Dates that are marked with a dagger () are tentative and subject to change. {: important}

Version Supported? Release date Unsupported date
1.35 Yes {{site.data.keyword.kubernetes_135_release_date}} {{site.data.keyword.kubernetes_135_unsupported_date}}
{: caption="Release timeline for {{site.data.keyword.containerlong_notm}} version 1.35" caption-side="bottom"}

Preparing to update

{: #prep-up-135}

For a complete list of changes that might impact your deployed apps when you update your cluster, review the community Kubernetes change log{: external} and IBM version change log for version 1.35. You can also review the Kubernetes helpful warnings{: external}. {: shortdesc}

Cluster autoscaler does not yet support version 1.35. Do not upgrade your cluster to version 1.35 if your cluster uses cluster autoscaler. {: important}

Istio add-on version 1.26 is not supported for IBM Cloud Kubernetes Service version 1.35 because the Istio add-on does not support Istio 1.29. Do not update to IBM Cloud Kubernetes Service version 1.35 if you use the add-on in your cluster. As an alternative, you can migrate from the Istio add-on to community Istio. {: important}

NodeLocal DNS enabled by default

{: #nodelocal-dns-135}

Starting with version 1.35, NodeLocal DNS is enabled by default on all worker nodes to improve DNS performance and reliability. NodeLocal DNS caches DNS queries locally on each worker node, which reduces latency and improves DNS availability. {: shortdesc}

Version 1.34 and earlier : NodeLocal DNS is opt-in. Enable NodeLocal DNS by adding the ibm-cloud.kubernetes.io/node-local-dns-enabled=true label to your worker nodes.

Version 1.35 and later : NodeLocal DNS is enabled by default on all worker nodes. Clusters that are upgraded to version 1.35 have NodeLocal DNS enabled automatically unless you opt out. NodeLocal DNS pods are recreated during the upgrade due to configuration changes.

Opting out of automatic NodeLocal DNS enablement

{: #nodelocal-dns-135-opt-out}

To prevent NodeLocal DNS from being automatically enabled when you upgrade to version 1.35, apply the following label to your worker nodes before you upgrade.

kubectl label node --all --overwrite "ibm-cloud.kubernetes.io/node-local-dns-disabled=true"

{: pre}

Special cases

{: #nodelocal-dns-135-special}

Zone-aware DNS enabled : If your cluster has zone-aware DNS enabled, NodeLocal DNS is not automatically enabled. Zone-aware DNS and NodeLocal DNS are mutually exclusive features.

NodeLocal DNS already enabled : If you previously enabled NodeLocal DNS in version 1.34 or earlier, your configuration is preserved and NodeLocal remains enabled. However, the DNS pods are recreated during the upgrade.

For more information about NodeLocal DNS, see Setting up NodeLocal DNS cache.