What happened?

Currently, setting CLUSTER_NAME requires boilerplate in every cluster override:

  holmes:
    additionalEnvVars:
      - name: CLUSTER_NAME
        value: dev-cluster

Proposal: Add a dedicated clusterName value (like there is in the robusta helm chart) that automatically sets the CLUSTER_NAME env var:

  holmes:
    clusterName: dev-cluster

I can implement this fix if needed.

What did you expect to happen?

A dedicated clusterName field that automatically injects the CLUSTER_NAME env var

How can we reproduce it (as minimally and precisely as possible)?

1. Deploy holmesgpt to any cluster
2. Observe required boilerplate:
   holmes:
   additionalEnvVars:
   • name: CLUSTER_NAME
     value: {cluster-name}
     This pattern must be repeated for every cluster deployment

Anything else we need to know?

No response