Updating the DataBus producer configuration
The steps in this section helps you to manually disable a flag that allows you to integrate Cloudera Data Services on premises 1.5.5 SP2 with Cloudera Observability on premises.
- Identify your Cloudera Data Services on premises namespace.
-
Edit the ConfigMap by adding the namespace
kubectl edit configmap databus-producer-conf-databus-producer -n
[***NAMESPACE***]
-
To identify your Cloudera Data Engineering service namespace, find the cluster ID in the Cloudera Data Engineering UI and use the format dex-base-<cluster_id>.
For example, if your Service ID is cluster-sbm2m4j9, cluster_id is sbm2m4j9, run export NAMESPACE=dex-base-sbm2m4j9
-
To identify your Cloudera Data Warehouse Database Catalog
namespace, find the catalog ID in the Cloudera Data Warehouse UI and use the format
warehouse-<catalog_id>.
For example, if your ID is 1769067981-6gk5, run export NAMESPACE=warehouse-1769067981-6gk5
-
To identify your Cloudera Data Engineering service namespace, find the cluster ID in the Cloudera Data Engineering UI and use the format dex-base-<cluster_id>.
-
In the databus-producer.xml file in Cloudera Data Warehouse and dbus-client.xml in
Cloudera Data Engineering, add the following property inside the
[***Configuration***] element:
<property> <name>observability.dbus.hostname.validation.enabled</name> <value>false</value> </property> - Save changes.
- Restart the pod.
- Run the kubectl rollout restart deployment command: <deployment-name> -n $NAMESPACE
- Check rollout status for kubectl by running the command <deployment-name> -n $NAMESPACE
