Update notes
This section describes the specific actions you need to complete to accurately plan and successfully perform the update. Consider this information as a supplement to the generic update procedures published in Operations Guide: Update to a patch version.
Cluster update schema
You can update to the 26.2.1 version from the following cluster version:
26.2 (2026-09-21) - patch update
For the detailed cluster update schema, refer to MOSK cluster update schema.
Patch update impact and maintenance windows planning
The following table provides details on the impact of a MOSK cluster update to a patch release within the 26.2 series.
Note
For the detailed workflow of update to a patch release, refer to Update to a patch version.
Updated component |
Impact on cloud users |
Impact on cloud workloads |
|---|---|---|
OpenStack and OpenSDN |
|
Open vSwitch networking - interruption of the North-South connectivity, depending on the type of virtual routers used by a workload:
OpenSDN networking - no impact |
Ceph |
~1% of read operations on object storage API may fail |
IO performance degradation for Ceph-backed virtual storage devices |
Host OS components |
No impact |
No impact |
Host OS kernel |
No expected performance impact |
Restart of instances due to the hypervisor reboot [0] |
Known issues during the update
Before updating the cluster, be sure to review the potential issues that may arise during the process and the recommended solutions to address them, as outlined in Known issues: Cluster update.
Pre-update actions
Note
If you have already completed some of the following actions before or after updating to 26.2, skip them.
Remove the custom horizon_db_purge image
If you have set a custom horizon_db_purge image using a ConfigMap as a
workaround for the known issue 67664, remove the
horizon_db_purge line from the ConfigMap before starting the update.
Remove the services left from the previous MKE upgrade
Before starting the update, remove the ucp-3-7-32-mosk and
ucp-images-check-3-7-32-mosk services that remain in Docker Swarm after
the previous MKE upgrade. Otherwise, the update may get stuck due to the
known issue 68577.
On an MKE manager node of the MOSK cluster, list the remaining MKE upgrade services:
sudo docker service ls --format '{{.Name}}' | grep -E '^ucp-(images-check-)?[0-9]+-[0-9]+-[0-9]+'
Example of system response:
ucp-3-7-32-mosk ucp-images-check-3-7-32-mosk
Remove each listed service, if any:
sudo docker service rm <serviceName>
Upgrade OpenStack to Epoxy
MOSK 26.1.2 is the last release version that supports OpenStack Caracal. Starting from MOSK 26.2, only OpenStack Epoxy and Gazpacho are supported. Therefore, if your MOSK cluster still runs OpenStack Caracal, upgrade it to Epoxy. For the procedure, see MOSK 26.1: Upgrade OpenStack.
Before the upgrade, review the following known issues. Some of them require actions that you must perform while the cluster is still running Caracal:
See also
Post-update actions
Close the MKE-specific firewall ports on the management cluster nodes
After the migration of the management cluster to k0s, the MKE-specific ports
are no longer used by any cluster component. For this reason, you can
optionally close TCP 2376, 2377, 7946, 12376, 12379-12387,
and UDP 7946 on the management cluster nodes. All other ports of the
management cluster remain required, including TCP 179, 10250,
12388 and UDP 4792. For details, see
Security Guide: Firewall configuration - MOSK management.
Switch to setting Ceph RGW DNS names using the ObjectStore spec definition
Note
Skip this action if your MOSK cluster has no customizations for TLS and DNS settings.
If your MOSK cluster has a non-default
ingressConfig.tlsConfig.publicDomain configuration or the
ingressConfig.tlsConfig.hostname parameter specified, switch to setting
RGW DNS names using the ObjectStore spec definition. This requirement is
part of the NGINX Ingress deprecation and migration to Application Gateway.
Configure the spec.objectStorage section of CephDeployment as follows:
spec:
objectStorage:
gatewayHTTPRoutes:
- name: <name-of-the-gateway-http-route> # name of the Gateway HTTP route
spec:
hostnames:
- <ingressConfig.tlsConfig.hostname>.<ingressConfig.tlsConfig.publicDomain> # custom TLS hostname and public domain values
objectStores:
- name: <object-store-name> # name of the ObjectStore (Ceph RGW) that migrated from the deprecated objectStorage.rgw
spec:
hosting:
dnsNames:
- <ingressConfig.tlsConfig.hostname>.<ingressConfig.tlsConfig.publicDomain> # custom TLS hostname and public domain values
See also
Remove the existing StorageClass for RGW instances named rgw-storage-class
Optional
With the introduction of support for multiple ObjectStore (Ceph RGW)
instances, the default StorageClass name for newly created buckets has
changed to <object-store-name>-bucket. The previously created
StorageClass for a single ObjectStore instance named rgw-storage-class
remains for backward compatibility. You can optionally remove the existing
StorageClass for RGW instances named rgw-storage-class if no
ObjectBucketClaims exist on your cluster with a reference to the old
storage class:
kubectl delete storageclass rgw-storage-class
All existing buckets are not affected, but for newly created ones, use
StorageClass with the new name.
Migrate NGINX Ingress to Application Gateway
Migrate your OpenStack, Ceph, and OpenSDN public endpoints from NGINX Ingress to Application Gateway. For detailed instructions, refer to Migrate public endpoints to Envoy Proxy.