How to Change a Cluster Name 📛

Komodor is a powerful platform for monitoring and troubleshooting Kubernetes clusters. As your infrastructure evolves, you may find the need to update the cluster names within Komodor to reflect changes accurately.

Fortunately, the process is straightforward and doesn't require deleting the cluster. Instead, you can update the cluster name by retaining the same API key and 'update' the agent.

In this article, we'll guide you through the steps to change a cluster name in Komodor without disrupting your monitoring setup.

  1. Go to the Komodor Services Page:Screenshot 2023-12-21 at 15.49.36.png

  2. Locate the Cluster you'd like to change the name of:
    Screenshot 2023-12-21 at 15.50.33.png

  3. Locate the related Cluster API Key in Integrations: Screenshot 2023-12-21 at 15.52.27.png
    If for whatever reason you aren't able to understand which cluster is related to which API key, feel free to open a ticket to support. 

  4. Retain API Key: It's important to note that you won't need to generate a new API key. The API key serves as a unique identifier for your cluster within Komodor. Retaining the same API key ensures continuity in monitoring and troubleshooting without interruptions.

  5. Update the Cluster Name: Within the terminal, while connected to the running cluster. Run the following command to 'update' the agent - locate the parameter that specifies the cluster name. This is the field you'll be modifying to reflect the updated name of your cluster. Follow the provided syntax and guidelines to ensure accurate configuration.

    helm repo add komodorio
    helm repo update
    helm upgrade --install komodor-agent komodorio/komodor-agent \
      --set apiKey=<YOUR_API_KEY_HERE> \
      --set clusterName=<NEW_CLUSTER_NAME_HERE> \

    Replace <your_existing_api_key> with your current API key and <new_cluster_name> with the desired name for your cluster.

  6. Verification: Confirm that the changes have taken effect by checking the Komodor Services Page. The updated cluster name should be reflected, and monitoring activities should continue seamlessly with the modified configuration.

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.