Updating proxy configuration in an existing Cloudera Data Engineering

Identifying the namespaces of Cloudera Data Engineering service and Virtual Cluster🔗

Each Cloudera Data Engineering service has one or more Virtual Clusters in it. Perform these steps to identify the namespaces of the Cloudera Data Engineering service and all the Virtual Clusters.

1. Identify the Cloudera Data Engineering service namespace:
   1. In the Cloudera console, click the Data Engineering tile. The Cloudera Data Engineering home page displays.
   2. On the left navigation menu, click Administration.
   3. In the Services column, click for the Cloudera Data Engineering service for which you want to identify the namespace.
   4. Note the Cluster ID displayed on the page and identify the Cloudera Data Engineering service namespace. For example, if the Cluster ID is cluster-5d88hpjx, then the Cloudera Data Engineering service namespace is dex-base-5d88hpjx.
   5. Note this namespace.
2. Identify the Virtual Cluster(s) namespace:
   1. In the Cloudera console, click the Data Engineering tile. The Cloudera Data Engineering home page displays.
   2. On the left navigation menu, click Administration.
   3. In the Virtual Clusters column, click for the Virtual Cluster for which you want to identify the namespace.
   4. Note the VC-ID displayed on the page and identify the Virtual Cluster namespace. For example, if the VC-ID is dex-app-6zqthvpq, then your Virtual Cluster namespace is also the same, that is dex-app-6zqthvpq.
   5. Note this namespace and repeat these steps for all Virtual Clusters.

Updating the proxy config🔗

Update the ConfigMap cdp-proxy-config present in the namespaces of the Cloudera Data Engineering service and the Virtual Cluster(s) using this command:

kubectl edit configmaps cdp-proxy-config -n [***NAMESPACE***]

For example,

kubectl edit configmaps cdp-proxy-config -n dex-base-2bs9t4kv

Restarting all the deployments🔗

After updating the ConfigMaps in all the relevant namespaces, restart all the deployments in Cloudera Data Engineering service and all the Virtual Clusters namespaces using this command:

kubectl -n [***NAMESPACE***] rollout restart deployment

For example,

kubectl -n dex-base-2bs9t4kv rollout restart deployment
kubectl -n dex-app-6zqthvpq rollout restart deployment