Update notes¶
This section describes the specific actions you as a Cloud Operator need to complete to accurately plan and successfully perform your Mirantis OpenStack for Kubernetes (MOSK) cluster update to the version 23.2. Consider this information as a supplement to the generic update procedure published in Operations Guide: Update a MOSK cluster.
Features¶
The MOSK cluster will obtain the newly implemented capabilities automatically with no significant impact on the update procedure.
Major component versions update¶
As part of the update to MOSK 23.2, the following automatic updates of major component versions will take place:
MKE 3.5 with Kubernetes 1.21 to 3.6 with Kubernetes 1.24
Ceph Pacific to Quincy
See also
Update impact and maintenance windows planning¶
The update to MOSK 23.2 does not include any version-specific impact on the cluster. To start planning a maintenance window, use the Operations Guide: Update a MOSK cluster standard procedure.
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 Cluster update known issues.
Pre-update actions¶
Disable the Instance High Availability service¶
While updating your cluster, the Instance High Availability service
(OpenStack Masakari) may not work as expected. Therefore, temporarily
disable the service by removing instance-ha
from the service list
in the OpenStackDeployment
custom resource.
Post-update actions¶
Upgrade Ubuntu to 20.04¶
In the next release series, MOSK will stop supporting Ubuntu 18.04. Therefore, Mirantis highly recommends upgrading an operating system on your cluster machines to Ubuntu 20.04 during the course of the MOSK 23.2 series by rebooting cluster nodes.
It is not mandatory to reboot all machines at once. You can reboot them one by one or in small batches, for example, if the maintenance window is limited in time.
Otherwise, the Cluster release update for the cluster running on Ubuntu 18.04 will become impossible.
For details on distribution upgrade, see Upgrade an operating system distribution.
Upgrade OpenStack to Yoga¶
MOSK supports the OpenStack Victoria version until September, 2023. MOSK 23.2 is the last release version where OpenStack Victoria packages are updated.
If you have not already upgraded your OpenStack version to Yoga, Mirantis highly recommends doing this during the course of the MOSK 23.2 series.
Make the OpenStack notifications available in StackLight¶
After the update, the notifications from OpenStack become unavailable in StackLight. On an attempt to establish a TCP connection to the RabbitMQ server, the connection is refused with the following error:
Could not establish TCP connection to any of the configured hosts
As a workaround, add the following annotation to
the openstack-rabbitmq-users-credentials
secret:
kubectl -n openstack patch secrets openstack-rabbitmq-users-credentials --type='json' -p='[{"op": "add", "path": "/metadata/annotations/foo", "value":"bar"}]'