Cloudera Docs

Upgrading from Cluster Connectivity Manager v1 to Cluster Connectivity Manager v2

Upgrading from Cluster Connectivity Manager v1 to Cluster Connectivity Manager v2 is available for customers who created their environments with Cluster Connectivity Manager v1. The upgrade requires no downtime. If your environment needs to be updated, you will see a notification printed in your environment details.

Both Cluster Connectivity Manager v1 and Cluster Connectivity Manager v2 provide the same functionality but version 2 is an improvement over version 1. Cluster Connectivity Manager v2 is more efficient in communicating with the Cloudera Control Plane and has a smaller footprint on the customer network.

The differences between Cluster Connectivity Manager v2 and Cluster Connectivity Manager v1 are related to improving reliability and efficiency. These differences are as follows:

  • Cluster Connectivity Manager v2 uses fewer agents (its agents are on FreeIPA nodes only), whereas Cluster Connectivity Manager v1 has a larger footprint, with its agents running across not only on FreeIPA nodes but also on Data Lake and Cloudera Data Hub nodes.

  • Cluster Connectivity Manager v2 uses the HTTPS protocol while Cluster Connectivity Manager v1 is based on the SSH protocol. The use of HTTPS makes Cluster Connectivity Manager v2 much more customer firewall friendly; it uses standard outbound ports which are allowed in almost all customer networks.

  • Since Cluster Connectivity Manager v2 uses HTTPS, it is more proxy-friendly. Customers can set up a proxy server such as Squid and inspect the underlying traffic to be more confident about the data that is being sent to the Cloudera Control Plane.

  • Cluster Connectivity Manager v2 uses token authentication.

  • Newer Cloudera services, such as Cloudera AI, Cloudera Data Engineering, Cloudera DataFlow, Cloudera Data Warehouse, and others, only support Cluster Connectivity Manager v2.

Before you begin

Prior to upgrading Cluster Connectivity Manager, you should ensure that:

  1. You are using the latest FreeIPA image. To upgrade your FreeIPA, follow the steps described in Upgrade FreeIPA.

  2. You have the network configured so that Cluster Connectivity Manager v2 endpoints are available. See ”Cloudera Cluster Connectivity Manager v2” in the AWSAzureGCP outbound network access destinations.

Steps

  1. If your environment should be updated from Cluster Connectivity Manager v1 to Cluster Connectivity Manager v2, you will see a "Time to upgrade Cluster Connectivity Manager version" notification similar to the following in your environment details:

  2. Upgrade Cluster Connectivity Manager either via Cloudera web interface or CLI:

    1. Cloudera web interface: Navigate to the Cloudera Management Console > Environments and click on the tile corresponding to a specific environment. Trigger the upgrade by clicking on the Upgrade button present on the UI element.

    2. CDP CLI: Use the following command: 
      cdp environments upgrade-ccm --environment <ENV_NAME_OR_CRN>

  3. The status of your environment changes while the upgrade is pending. All environment components get upgraded (FreeIPA, Data Lake, and then Cloudera Data Hub clusters). Check the event history to confirm that the upgrade has been completed. Once the upgrade has been completed, the status of the environment changes back to “Running”. If an error occurs during the process, Cloudera rolls back the upgrade and reverts the environment to Cluster Connectivity Manager v1.