Day-2 operations workflow

TechPreview since MCC 2.26.0 (17.1.0 and 16.1.0)

The workflow of the day-2 operations API that use Container Cloud or custom modules is as follows:

If you are a module consumer

1. Select one of the following options:

   • If you do not intend to use custom modules, skip to step 2.

   • If you intend to use custom modules:

     1. Contact the module creator to obtain the link to the module and its SHA256.

     2. Add the module to an existing HostOSConfigurationModules (hocm) object or create a new hocm object. For details, see Container Cloud API Reference: HostOSConfigurationModules custom resource and Add a custom module to a MOSK deployment.

2. Add the configuration of the Container Cloud or custom module to an existing HostOSConfiguration (hoc) object or create a new hoc object with the following details:

   1. Add the required configuration details of the module.

   2. Set the selector for machines to apply the configuration.

   For details, see Container Cloud API Reference: HostOSConfiguration custom resource along with HostOSConfiguration and HostOSConfigurationModules concepts.

3. Optional. Retrigger the same successfully applied module configuration. For details, see Retrigger a module configuration.

If you are a custom module creator

1. Create a custom configuration module as required. For reference, see Format and structure of a module package and Modules provided by MOSK.

2. Publish the module in a repository from which the cloud operator can fetch the module.

3. Share the module details with the cloud operator.

The following diagram illustrates the high-level overview of the day-2 operations API: