Re-onboarding a cluster

Learn how to re-upload your Kubernetes cluster, ensuring its data continuation

You may encounter situations where re-uploading a cluster is necessary. For example, if you disconnect a cluster, you might later need to upload it again to restore its visibility and management within the PerfectScale.

When you reconnect your cluster using the standard configuration, PerfectScale will assign it a new ID and treat it as a new cluster. The historical data from the previous cluster will remain associated with the original cluster rather than the newly connected one. To restore your cluster while keeping it associated with its historical data, follow the instructions below.

How to retrieve clusterUID

To find the Cluster ID for the cluster you want to re-upload, go to the Overview page, click the three-dot menu next to the desired cluster, and select Copy Cluster UID. Your clusterUID is now copied to the clipboard.

clusterUID

How to retrieve credentials

To retrieve the clusterName, clientID, and clientSecret by executing the following commands accordingly:

clusterName

kubectl -n perfectscale describe deployment perfectscale-exporter | grep CLUSTER_NAME

clientID

kubectl -n perfectscale get secret perfectscale-exporter-secret -o jsonpath="{.data.clientId}" | base64 --decode

clientSecret

kubectl -n perfectscale get secret perfectscale-exporter-secret -o jsonpath="{.data.clientSecret}" | base64 --decode

Re-installing PerfectScale Agent

While installing the PerfectScale Agent (4), ensure that you use the same clusterName and clusterUID as previously used.

Use the following command to re-upload the cluster:

helm upgrade --install -n perfectscale --create-namespace perfectscale \
      --set secret.create=true \
      --set secret.clientId=your_clientId \
      --set secret.clientSecret=your_clientSecret \
      --set settings.clusterName=your_cluster_name \
      --set settings.clusterID=your_clusterUID \
      perfectscale/exporter

If taints and tolerations are defined in the node pool, you must include them in the command too, so it will appear like this:

helm upgrade --install -n perfectscale --create-namespace perfectscale \      
      --set secret.create=true \
      --set secret.clientId=your_clientId \
      --set secret.clientSecret=your_clientSecret \
      --set settings.clusterName=your_cluster_name \
      --set tolerations[0].key=node_pool \
      --set tolerations[0].operator=Equal \
      --set tolerations[0].value=tooling \
      --set kube-state-metrics.tolerations[0].key=node_pool,kube-state-metrics.tolerations[0].value=tooling,kube-state-metrics.tolerations[0].operator=Equal \
      --set settings.clusterID=your_clusterUID \
      perfectscale/exporter

Re-installing PerfectScale Automation Agent

If you've re-uploaded the cluster where PerfectScale Automation was previously operational and wish to resume using Automation for that cluster, it's important to re-install the Automation Agent. This step will ensure that your cluster remains continuously optimized, tailored to your previously configured CR.

When re-installing Automation Agent, run the following command:

helm upgrade --install -n perfectscale psc-autoscaler \
      --set settings.clusterID=your_clusterUID \
      --set secret.create=false \
      perfectscale/psc-autoscaler

If taints and tolerations are defined in the node pool, you must include them in the command too, so it will appear like this:

helm upgrade --install -n perfectscale psc-autoscaler \
      --set settings.clusterID=your_clusterUID \
      --set tolerations[0].key=node_pool \
      --set tolerations[0].operator=Equal \
      --set tolerations[0].value=tooling \
      --set secret.create=false \
      perfectscale/psc-autoscaler