Container Cloud¶

This section provides information about deprecated and removed functionality in Mirantis Container Cloud services.

OpenStack cloud provider¶

Deprecated	Container Cloud 2.28.4 (Cluster release 16.3.4)
Unsupported	Container Cloud 2.29.0 (Cluster release 16.4.0)
Details	Suspended support for OpenStack-based deployments for the sake of the MOSK product. Simultaneously, ceased performing functional integration testing of the OpenStack provider and removed the possibility to update an OpenStack-based cluster to Container Cloud 2.29.0 (Cluster release 16.4.0). Therefore, the final supported version for this cloud provider is Container Cloud 2.28.5 (Cluster release 16.3.5). If you still require the feature, contact Mirantis support for further information.

Deprecated

Container Cloud 2.28.4 (Cluster release 16.3.4)

Unsupported

Container Cloud 2.29.0 (Cluster release 16.4.0)

Details

Suspended support for OpenStack-based deployments for the sake of the MOSK product. Simultaneously, ceased performing functional integration testing of the OpenStack provider and removed the possibility to update an OpenStack-based cluster to Container Cloud 2.29.0 (Cluster release 16.4.0).

Therefore, the final supported version for this cloud provider is Container Cloud 2.28.5 (Cluster release 16.3.5). If you still require the feature, contact Mirantis support for further information.

Reference Application for workload monitoring¶

Deprecated	Container Cloud 2.28.0 (Cluster release 16.3.0)
Unsupported	Container Cloud 2.28.3 (Cluster release 16.3.3)
Details	Deprecated support for Reference Application on non-MOSK clusters. Due to this deprecation, if the `RefAppDown` alert is firing in the cluster, disable `refapp.enabled` to prevent unnecessary alerts. Note For the feature support on MOSK deployments, refer to Deploy your first cloud application using automation.

The maxWorkerUpgradeCount parameter¶

Deprecated	Container Cloud 2.27.0 (Cluster releases 17.2.0 and 16.2.0)
Unsupported	To be decided
Details	Deprecated the `maxWorkerUpgradeCount` parameter of the `Cluster` object. Use the `concurrentUpdates` parameter in the `UpdateGroup` object instead.

VMware vSphere-based clusters¶

Deprecated	Container Cloud 2.27.2 (Cluster release 16.2.2)
Unsupported	Container Cloud 2.27.3 (Cluster release 16.2.3)
Details	Suspended support for VMware vSphere-based deployments, including attachment of existing Mirantis Kubernetes Engine (MKE) clusters that were originally not deployed by Container Cloud. Simultaneously, ceased performing functional integration testing of the vSphere provider and removed the possibility to update a vSphere-based cluster to Container Cloud 2.27.3 (Cluster release 16.2.3). Therefore, the final supported version for this cloud provider is Container Cloud 2.27.2 (Cluster release 16.2.2). If you still require the feature, contact Mirantis support for further information.

Deprecated

Container Cloud 2.27.2 (Cluster release 16.2.2)

Unsupported

Container Cloud 2.27.3 (Cluster release 16.2.3)

Details

Suspended support for VMware vSphere-based deployments, including attachment of existing Mirantis Kubernetes Engine (MKE) clusters that were originally not deployed by Container Cloud.

Simultaneously, ceased performing functional integration testing of the vSphere provider and removed the possibility to update a vSphere-based cluster to Container Cloud 2.27.3 (Cluster release 16.2.3).

Therefore, the final supported version for this cloud provider is Container Cloud 2.27.2 (Cluster release 16.2.2). If you still require the feature, contact Mirantis support for further information.

Regional clusters¶

Deprecated	Container Cloud 2.25.0 (Cluster releases 17.0.0 and 16.0.0)
Unsupported	Container Cloud 2.26.0 (Cluster releases 17.1.0 and 16.1.0)
Details	Suspended support for regional clusters and several regions on a single management cluster. Simultaneously, ceased performing functional integration testing of the feature and removed the related code in Container Cloud 2.26.0. If you still require this feature, contact Mirantis support for further information.

Bootstrap v1¶

Deprecated	Container Cloud 2.25.0 (Cluster releases 17.0.0 and 16.0.0)
Unsupported	Container Cloud 2.26.0 (Cluster releases 17.1.0 and 16.1.0)
Details	Deprecated the bootstrap procedure using Bootstrap v1 in favor of Bootstrap v2. For new bootstrap procedure, see Deploy a management cluster.

Attachment of MKE clusters¶

Deprecated	Container Cloud 2.24.0 (Cluster release 14.0.0)
Unsupported	Container Cloud 2.24.0 (Cluster release 14.0.0)
Details	Suspended support for attachment of existing Mirantis Kubernetes Engine (MKE) clusters that were originally not deployed by Container Cloud. Also suspended support for all related features, such as sharing a Ceph cluster with an attached MKE cluster.

IAM API and IAM CLI¶

Deprecated	Container Cloud 2.15.0 (Cluster releases 7.5.0 and 5.22.0)
Unsupported	Container Cloud 2.18.0 (Cluster releases 11.2.0 and 7.8.0)
Details	Deprecated the `iam-api` service and IAM CLI (the iamctl command). The logic of the `iam-api` service required for Container Cloud is moved to `scope-controller`.

SSH-enabled user names¶

Deprecated	Container Cloud 2.7.0 (Cluster release 5.14.0)
Unsupported	Container Cloud 2.9.0 (Cluster releases 6.16.0 and 5.16.0)
Details	Replaced all existing SSH user names, such as `ubuntu`, with the universal `mcc-user` user name. Since Container Cloud 2.9.0, SSH keys are managed only for `mcc-user`.

DISABLE_OIDC flag for TLS¶

Deprecated	Container Cloud 2.13.0 (Cluster releases 7.3.0 and 5.20.0)
Unsupported	Container Cloud 2.14.0 (Cluster releases 7.4.0 and 5.21.0)
Details	Removed the `DISABLE_OIDC` flag required to be set for custom TLS Keycloak and web UI certificates during a management cluster deployment. Do not set this parameter anymore in `bootstrap.env`. To use your own TLS certificates for Keycloak, refer to Configure TLS certificates for cluster applications.