Managing multiple clusters for watsonx.governance

You can distribute governance activities across multiple servers and sync between the primary governance server and remote servers. Use multiple servers to isolate production assets on one server and control access to them for greater security.

Who needs to complete this task?

You must be a instance administrator to do the tasks related to designating multiple clusters. Instance admins can configure watsonx.governance™ clusters that they administer.

When do you need to complete this task?

Complete this task when your governance assets are mature enough to merit distribution of their governance activities across multiple servers for segregated monitoring.

An administrator for watsonx.governance who collects the metadata for model activity might want to put physical models on one server and govern them on another for security or accessibility purposes. For example, if an administrator wants to track but not to manage the model's general lifecycle, such as evaluating or deploying them.

In this example, the administrator can set up a primary governance cluster used for viewing model information. They then set up one or multiple remote clusters where models are uploaded, evaluated and deployed. The watsonx.governance remote clusters are configured to send data to the primary governance cluster automatically whenever there is model activity. The metadata for the models on primary governance cluster are synced when it receives the updated data. The physical models live only on remote clusters for their lifecycle.