Reverting a cluster to a stand-alone cluster for watsonx.governance
You can disconnect a remote cluster and revert to a stand-alone cluster. You can also revert a primary governance cluster to a stand-alone cluster if all remote clusters are disconnected. Reverting clusters to stand-alone clusters releases any additional resources that are consumed by the clusters after configuration.
- Who needs to complete this task?
- You must be the instance administrator of the watsonx.governance⢠cluster that is being reverted, and work with admins of impacted clusters.
- When do you need to complete this task?
- Complete this task when you have remote clusters or primary governance clusters with model tracking activities that you want to cease and you want to reallocate the additional resources consumed by the clusters.
About this task
- Reverting a primary governance cluster
-
- Information about assets on remote clusters that were previously synced to this governance cluster are not purged, but they become stale as they stop getting updates from remote clusters.
-
Any new alerts from assets on remote clusters are not available.
-
Incomplete and potentially inconsistent information shown if you revert and then re-enable this cluster.
- Reverting a remote cluster
-
-
Information about assets on this cluster is no longer be published to the remote governance cluster.
-
Assets on this cluster are no longer tracked under AI use case and lifecycle tracking is incomplete.
-
Incomplete and potentially inconsistent information shown if you revert and then re-enable this cluster.
-
Procedure
To revert the clusters to stand-alone clusters: