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.

Automatically propagate Salesforce configuration to all clusters¶

You can enable automatic propagation of the Salesforce configuration of your management cluster to the related MOSK clusters using the autoSyncSalesForceConfig=true flag added to the Cluster object of the management cluster. This option allows for automatic update and sync of the Salesforce settings on all your clusters after you update your management cluster configuration.

You can also set custom settings for MOSK clusters that always override automatically propagated Salesforce values.

Enable propagation of Salesforce configuration using the management console¶

Log in to the MOSK management console as m:kaas@global-admin or m:kaas@writer.
In the Clusters tab, click the More action icon in the last column of the required management cluster and select Configure.
In the Configure cluster window, navigate to StackLight > Salesforce and select Salesforce Configuration Propagation To Managed Clusters.
Click Update.

Once the automatic propagation applies, the Events section of the corresponding MOSK cluster displays the following message: Propagated Cluster Salesforce Config From Management <clusterName> Cluster uses SalesForce configuration from management cluster.

Note

To set custom Salesforce settings for your MOSK clusters that will override the related management cluster settings, refer to the optional step in Enable propagation of Salesforce configuration using CLI.

Enable propagation of Salesforce configuration using CLI¶

Download your management cluster kubeconfig:
1. Log in to the MOSK management console with the m:kaas:namespace@operator or m:kaas:namespace@writer permissions.
2. Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.
3. Expand the menu of the tab with your user name.
4. Click Download kubeconfig to download kubeconfig of your management cluster.
5. Log in to any local machine with kubectl installed.
6. Copy the downloaded kubeconfig to this machine.

In the Cluster objects of the required MOSK cluster, remove all Salesforce settings that you want to automatically sync with the same settings of the management cluster:

kubectl --kubeconfig <mgmtClusterKubeconfigPath> edit -n <moskClusterProjectName> cluster <moskClusterName>

From the StackLight values section, remove the following Salesforce parameters:

spec:
  ...
  providerSpec:
    value:
      helmReleases:
      - name: stacklight
        values:
          ...

alertmanagerSimpleConfig.salesForce.enabled
alertmanagerSimpleConfig.salesForce.auth
sfReporter.salesForceAuth
sfReporter.enabled
sfReporter.cronjob

For details about these parameters, refer to StackLight configuration parameters for Salesforce.

In the management section of the management cluster Cluster object, add the autoSyncSalesForceConfig: true flag:

kubectl --kubeconfig <kubeconfigPath> edit -n <projectName> cluster <managementClusterName>

spec:
  ...
  providerSpec:
    value:
      kaas:
      ...
        management:
          ...
          autoSyncSalesForceConfig: true

Note

If the autoSyncSalesForceConfig is not set to any value, automatic propagation is disabled.

Once enabled, the following Salesforce parameters are copied to all MOSK clusters where these settings were not configured yet:

alertmanagerSimpleConfig.salesForce.enabled
alertmanagerSimpleConfig.salesForce.auth
sfReporter.salesForceAuth
sfReporter.enabled
sfReporter.cronjob

The existing Salesforce settings of MOSK clusters will not be overridden after you enable automatic propagation.

To verify the automatic propagation status:

kubectl edit helmbundles <moskClusterName> -n <moskClusterProjectName>

Optional. Set custom Salesforce settings for your MOSK cluster to override the related management cluster settings. Add the required custom settings to the StackLight values section of the corresponding Cluster object of your MOSK cluster:
```
spec:
  ...
  providerSpec:
    value:
      helmReleases:
      - name: stacklight
        values:
          ...
```
For details, refer to Configure StackLight and StackLight configuration parameters for Salesforce.

Note

Custom settings are not overridden if you update the management cluster settings for Salesforce.