Cluster update¶
Updating a MOSK cluster ensures that the system remains secure, efficient, and up-to-date with the latest features and performance improvements, as well as receives fixes for the known CVEs. This section provides comprehensive details and step-by-step procedures to guide you through the process of updating your cluster.
Cluster updates in MOSK encompass both management cluster and MOSK cluster updates:
Update type |
Description |
|---|---|
Management cluster update |
The management cluster update is performed automatically as long as the release of each MOSK cluster has either supported or deprecated status in the new version of MOSK management. In case any of the clusters managed by MOSK management is about to get an unsupported status as a result of an update, the MOSK management cluster updates will get blocked till the cluster gets to a later release. For the cluster release statuses, refer to Cluster support statuses. |
Cluster major update |
Major cluster update is initiated by a cloud operator through the MOSK management console. The update procedure is automated and covers all the life cycle management modules of the cluster that include OpenStack, Tungsten Fabric, Ceph, and StackLight. Refer to Update to a major version for the procedure. Version-specific considerations Before the MOSK 24.1 series, if between the major releases you apply at least one patch release belonging to the N series, you should obtain the last patch release in the series to be able to update to the N+1 major release version. Since MOSK 24.1.5, the product introduces a new approach to cluster updates. For details, refer to Cluster update scheme and Update schemes comparison. |
Cluster patch update |
Patch cluster update is initiated by a cloud operator through the MOSK management console. The update procedure is automated and covers all the life cycle management modules of the cluster that include OpenStack, Tungsten Fabric, Ceph, and StackLight. Refer to Update to a patch version for the procedure. Version-specific considerations Since MOSK 24.1.5, the product introduces a new approach to cluster updates. For details, refer to Cluster update scheme and Update schemes comparison. |
- Update to a major version
- Update to a patch version
- Verify the management cluster status before MOSK update
- Change the upgrade order of a machine
- Configure the parallel update of worker nodes
- Create update groups for worker machines
- Granularly update MOSK using the ClusterUpdatePlan object
- Configure update auto-pause
- Calculate a maintenance window duration for update Deprecated