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] Grafana Disabled in Kubecost #3831

Open
2 tasks done
madhubalaravi opened this issue Feb 3, 2025 · 0 comments
Open
2 tasks done

[Bug] Grafana Disabled in Kubecost #3831

madhubalaravi opened this issue Feb 3, 2025 · 0 comments
Labels
bug Something isn't working needs-triage

Comments

@madhubalaravi
Copy link

Kubecost Helm Chart Version

2.4.3

Kubernetes Version

1.30.6

Kubernetes Platform

AKS

Description

We are experiencing an issue where Grafana is showing as disabled in our Kubecost setup, despite using an existing Grafana deployment. The Grafana instance is accessible and functioning independently, but Kubecost does not recognize it as enabled.

Additional Information:

The Grafana dashboard is accessible from the Kubecost Diagnostic page but not from the Kubecost Container Sizing Recommendation page.
We have referred to the Kubecost documentation for configuring an existing Grafana deployment.

Steps to reproduce

Here is the values file.

global:
prometheus:
enabled: false
fqdn: https://prometheusxxx.xx.com
grafana:
enabled: false
domainName: https://grafanaxxx.xx.com
scheme: "https"
proxy: false
fqdn: https://grafanaxxx.xx.com

grafana:
grafana.ini:
server:
serve_from_sub_path: false
root_url: "https://grafanaxxx.xx.com"

kubecostProductConfigs:
grafanaURL: "https://grafanaxxx.xx.com"

Expected behavior

  • Grafana should be recognized as enabled in the Kubecost setup.
  • The Grafana dashboard should be accessible from all relevant Kubecost pages, including the Diagnostic page and the Container Sizing Recommendation page.
  • Kubecost should correctly integrate with the existing Grafana deployment, allowing seamless access to Grafana dashboards and metrics.

Impact

No response

Screenshots

No response

Logs

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.
@madhubalaravi madhubalaravi added bug Something isn't working needs-triage labels Feb 3, 2025
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

1 participant