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

Now, 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.

Configure host names for cluster machines¶

TechPreview

You can enable custom host names for cluster machines so that any machine host name in a particular management cluster and its MOSK clusters matches the related Machine object name. For example, instead of the default kaas-node-<UID>, a machine host name will be master-0. The custom naming format is more convenient and easier to operate with.

Note

After you enable custom host names on an existing management cluster, names of all newly deployed machines in this cluster and its MOSK clusters will match machine host names. Existing host names will remain the same.

If you are going to clean up a management cluster with this feature enabled after cluster deployment, make sure to manually delete machines with existing non-custom host names before cluster cleanup to prevent cleanup failure. For details, see Remove a management cluster.

You can enable custom host names during management cluster bootstrap during initial cluster configuration. For details, see Deploy a management cluster. To enable the feature on an existing cluster, see the procedure below.

To enable custom host names on an existing management cluster:

Open the Cluster object of the management cluster for editing:
```
kubectl edit cluster <mgmtClusterName>
```
In the spec.providerSpec.value.kaas.regional section of the required region, find the required provider name under helmReleases and add customHostnamesEnabled: true under values.config. For example:
```
regional:
 - helmReleases:
   - name: baremetal-provider
     values:
       config:
         allInOneAllowed: false
         customHostnamesEnabled: true
         internalLoadBalancers: false
```
The configuration applies in several minutes after the bare metal provider Pods restart automatically.

Verify that customHostnames is present in the provider ConfigMap:

kubectl -n kaas get configmap provider-config-<providerName> -o=yaml | grep customHostnames