Cloudera Docs

Using classic clusters with a non-transparent proxy

If your organization has a non-transparent proxy on the Cloudera Manager/Knox node, the following steps must be performed prior to classic cluster registration.

When you register a cluster in Cloudera as a classic cluster, Cloudera installs Cluster Connectivity Manager on the Cloudera Manager/Knox node of CDH and HDP clusters to establish connection between the on-premise cluster and Cloudera, allowing communication with the Cloudera Control Plane to kick off replication jobs on schedule. To do this, Cluster Connectivity Manager must be able to connect to the outside of the Data Center.

Steps

Create the following file on the Cloudera Manager node (in case of a CDH or Cloudera Private Cloud Base cluster) or on the Knox node (in case of an HDP cluster):

/etc/cdp/proxy.env
The file should include a proxy link. The format of the file should be:
https_proxy=http://<username>:<password>@<proxy.com>

  • The <username> and <password> should be replaced with an actual username that allows access to the proxy.

  • The <proxy.com> should be replaced with the URL of the proxy server.

Once you’ve performed these steps, you can proceed to registering your cluster in Cloudera.