Reactivating a deactivated Kubernetes cluster

Products

• CloudHealth

Issue/Introduction

Once a cluster has been manually deactivated in the Clusters page, that action is permanent and you cannot resurrect a cluster with the same name and UID as the deactivated one.

A cluster is uniquely defined by its UID and name.  If a cluster is accidentally deactivated and the goal is for it to start collecting again, it must be treated as a new cluster creation in the CloudHealth platform.

Resolution

This can be achieved in 1 of the following 2 ways:

1. If the deactivated cluster has no UID, then deploying a more recent version of the Kubernetes agent (which collects UID) will ensure that the cluster will be treated as a new cluster.  You are allowed to have more than 1 cluster with the same name, so long as the UID is distinct.
2. If the deactivated cluster has a UID, then you would need to update the cluster name env variable used in the Kubernetes agent install to define a new cluster name, which will ensure that a new cluster is created.