1.23 version information and update actions
Kubernetes version 1.23 is no longer supported. Update your cluster to at least version 1.24 as soon as possible.
Review information about version 1.23.
IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.23 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.
For more information about Kubernetes project version 1.23, see the Kubernetes change log
Release timeline
The following table includes the expected release timeline for version 1.23 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.
Dates that are marked with a dagger (†) are tentative and subject to change.
| Version | Supported? | IBM Cloud Kubernetes Service release date |
IBM Cloud Kubernetes Service unsupported date |
|---|---|---|---|
| 1.23 | Yes | 09 Feb 2022 | 08 May 2023 † |
Preparing to update
This information summarizes updates that are likely to have and impact on deployed apps when you update a cluster to version 1.23. For a complete list of changes, review the community Kubernetes change log and IBM version change log for version 1.23. You can also review the Kubernetes helpful warnings.
Kubernetes version 1.23 becomes unsupported on 08 May 2023. Update your cluster to at least version 1.24 as soon as possible.
Update before master
The following table shows the actions that you must take before you update the Kubernetes master.
| Type | Description |
|---|---|
| Unsupported: CoreDNS wildcard queries via Kubernetes plugin | CoreDNS no longer supports wildcard DNS queries via the Kubernetes plugin. Applications using such queries must be updated to use an alternative DNS query method. |
| Kubernetes service IP advertisement over BGP | If you are using Calico's Kubernetes Service IP Advertisement over BGP feature, you need to add the service IP CIDRs that you want to advertise to the default BGP configuration resource. In previous releases, the entire service IP range was advertised by setting an environment variable
in the calico-node daemonset. |
Update after master
The following table shows the actions that you must take after you update the Kubernetes master.
| Type | Description |
|---|---|
| Operator Lifecycle Manager (OLM) install no longer managed | OLM is no longer installed nor managed by IBM. Existing installs are unchanged and no longer managed after the update. If you are using the OLM components then you must manage updates. If unused, you may uninstall the OLM components. Refer to the open source documentation for information on available resources including how to install a new instance of OLM on your cluster. |
| Recreate volume snapshots | Volume snapshots must be recreated after the update. Run kubectl get volumesnapshots -A to get a list of volume snapshots. |