Configuring a remote cluster for watsonx.governance with direct connection
You can distribute governance activity by configuring a remote cluster that is connected to the primary governance cluster. Governance data is synced between the clusters.
Multiple watsonx.governance™ remote clusters send governance activity data to one watsonx.governance primary governance cluster where all data from the cluster group can be viewed.
- Who needs to complete this task?
- You must be the instance administrator of the watsonx.governance cluster that is being configured.
- When do you need to complete this task?
- Complete this task when you want to connect a watsonx.governance cluster to a primary governance
cluster with a direct connection only.
Alternatively, see Configuring a remote cluster for watsonx.governance with a custom governance connector if you need to set up an intermediary repository for syncing data to the primary governance cluster.
Before you begin
- watsonx.governance installed on a stand-alone cluster
- A primary governance cluster
- A certificate (See Using a CA certificate to connect to internal servers from the platform)
About this task
Before you designate a remote cluster, be aware that data on the remote cluster remains even after you revert the remote cluster to a stand-alone cluster. Reverting the remote cluster causes disruption for data syncing and might result in stale data.
Procedure
To designate a remote cluster with a direct connection to the primary governance cluster: