Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] unable to change cluster name #3771

Open
2 tasks done
GurayCetin opened this issue Dec 12, 2024 · 3 comments
Open
2 tasks done

[Bug] unable to change cluster name #3771

GurayCetin opened this issue Dec 12, 2024 · 3 comments
Labels
bug Something isn't working needs-triage

Comments

@GurayCetin
Copy link

Kubecost Helm Chart Version

2.4.3

Kubernetes Version

v1.30.5-gke.1443001

Kubernetes Platform

GKE

Description

I cannot change the cluster name, which is currently set to cluster-one. Despite adding the clusterName argument to the values.yaml, it was added as a second cluster instead. I tried deleting it, but the message 'You found an enterprise feature!' still appears on the interface, preventing me from using the Kubecost UI

Steps to reproduce

  1. clusterName argument is added to values.yaml to change cluster name.

Expected behavior

if i remove the clusterName from values.yaml, i would expect that 'You found an enterprise feature! message is disappeared.

Impact

No response

Screenshots

No response

Logs

No response

Slack discussion

No response

Troubleshooting

  • I have read and followed the issue guidelines and this is a bug impacting only the Helm chart.
  • I have searched other issues in this repository and mine is not recorded.
@GurayCetin GurayCetin added bug Something isn't working needs-triage labels Dec 12, 2024
@GurayCetin GurayCetin changed the title [Bug] cannot change cluster name [Bug] unable to change cluster name Dec 12, 2024
@jkiran13
Copy link

I faced the same issue. To resolve it, try re-installing it with cluster name at both prometheus.server.global.external_labels.cluster_id and kubecostProductConfigs.clusterName in values.yaml

Below is sample:

image
image

It worked for me !

@GurayCetin
Copy link
Author

enterprise

I have configured the values.yaml as you stated and kubecost is showing it's another cluster and asking for enterprise.

@jkiran13
Copy link

jkiran13 commented Dec 13, 2024

Chances are that prometheus has got 2 different names stored for the cluster - cluster-one (default by kubecost) and the one you provided. This detects unified multi clusters and hence prompts as an enterprise feature.

Do a restart for prometheus pod
kubectl rollout restart deployment <prometheus-deployment-name> -n <prometheus-namespace>

and still if it does not then re-install the chart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage
Projects
None yet
Development

No branches or pull requests

2 participants