Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

UpdateGroup resource¶

Available since Container Cloud 2.27.0 (17.2.0 and 16.2.0)

This section describes the UpdateGroup custom resource (CR) used in the management API to configure update concurrency for specific sets of machines or machine pools within a cluster. This resource enhances the update process by allowing a more granular control over the concurrency of machine updates. This resource also provides a way to control the reboot behavior of machines during a Cluster release update.

The UpdateGroup CR contains the following fields:

apiVersion
API version of the object that is kaas.mirantis.com/v1alpha1.
kind
Object type that is UpdateGroup.
metadata
Metadata of the UpdateGroup CR that contains the following fields. All of them are required.
- name
  Name of the UpdateGroup object.
- namespace
  Project where the UpdateGroup is created.
- labels
  Label to associate the UpdateGroup with a specific cluster in the cluster.sigs.k8s.io/cluster-name: <cluster-name> format.
spec
Specification of the UpdateGroup CR that contains the following fields:
- index
  Index to determine the processing order of the UpdateGroup object. Groups with the same index are processed concurrently.
  
  The update order of a machine within the same group is determined by the upgrade index of a specific machine. For details, see Change the upgrade order of a machine.
- concurrentUpdates
  Number of machines to update concurrently within UpdateGroup.
- rebootIfUpdateRequires
  Technology Preview. Available since Container Cloud 2.28.0 (17.3.0 and 16.3.0). Automatic reboot of controller or worker machines of an update group if a Cluster release update involves node reboot, for example, when kernel version update is available in new Cluster release. You can set this parameter for management or MOSK clusters.
  
  Boolean. By default, true on management clusters and false on MOSK clusters. On MOSK clusters:
  
  If set to true, related machines are rebooted as part of a Cluster release update that requires a reboot.
  
  If set to false, machines are not rebooted even if a Cluster release update requires a reboot.
  
  Caution
  
  During a distribution upgrade, machines are always rebooted, overriding rebootIfUpdateRequires: false.

Configuration example:

apiVersion: kaas.mirantis.com/v1alpha1
kind: UpdateGroup
metadata:
  name: update-group-example
  namespace: my-cluster-ns
  labels:
    cluster.sigs.k8s.io/cluster-name: my-cluster
spec:
  index: 10
  concurrentUpdates: 2
  rebootIfUpdateRequires: false