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

Disable Grafana by Default #1569

Closed
teevans opened this issue Jul 20, 2022 · 9 comments
Closed

Disable Grafana by Default #1569

teevans opened this issue Jul 20, 2022 · 9 comments
Assignees
Labels
enhancement New feature or request stale

Comments

@teevans
Copy link
Member

teevans commented Jul 20, 2022

Following up here on an email thread with AjayTripathy and nealormsbee.

Sounds like we're ready to make the switch to remove our shipped version of grafana by default.

AjayTripathy / nealormsbee

  • What are the steps to get this done?

gz#2222

(related to Zendesk ticket #2222)

┆Issue is synchronized with this Jira Task by Unito

@nealormsbee
Copy link
Member

@teevans I'll read through the Helm chart again to see if there are other considerations. Nominally, defaulting grafana.enabled = false in values.yaml.

That might be it, but there may be a little more. Broadcasting this change to users would also be good.

@dwbrown2
Copy link
Contributor

@AjayTripathy can you share the broader gameplan here so we have context?

@AjayTripathy
Copy link
Contributor

Note on implementation is you need to also set proxy=false

Here's my thoughts on broader plan. We should announce in patch notes that we're setting this to off but will continue to support byo grafana and community dashboards. Then over the next few releases we should remove grafana entirely from our app and only support byo+an integration with our dashboards.

@LaikaN57
Copy link
Contributor

Config snippet from a mostly disabled grafana (for whatever it is worth in this discussion):

# Configure how we interface with Grafana - we aren't running it ourselves in
# this stack, but instead we're leveraging the one in the observability
# platform.
grafana:
  # -- Create datasources in the [REDACTED] namespace
  namespace_datasources: [REDACTED]
  datasources:
    # -- No need to connect the datasources - its already setup to connect to Prometheus
    enabled: false
  sidecar:
    dashboards:
      enabled: false
    datasources:
      defaultDatasourceEnabled: false
global:
  # https://github.com/kubecost/docs/blob/master/custom-prom.md#custom-grafana
  #
  # Undocumented, but both "enabled" and "proxy" must be false in combination.
  grafana:
    # -- Disable management of our own internal Grafana service
    enabled: false
    # -- Disable creating the /grafana proxy url in the kubecost nginx
    # config, it must be disabled to tell Kubecost to use the grafanaURL we
    # give it.
    proxy: false

@dwbrown2
Copy link
Contributor

dwbrown2 commented Aug 9, 2022

Thanks for sharing @LaikaN57!

@AjayTripathy I still think this needs a little more thought from a product perspective. I doubt most users will go install all dashboards unless they are easily bundled.

@AjayTripathy
Copy link
Contributor

I'm supportive of continuing to bundle here-- I think this is just a question of turning grafana off by default? Set it to true and you'll still get the whole bundle. Open to additional feedback on that plan though!

@nickolashkraus
Copy link

nickolashkraus commented Nov 2, 2022

As a side note, when disabling Grafana (global.grafana.enabled=false) if global.grafana.proxy=true, which is the default, the cost-analyzer-frontend Pod will crashloop:

nginx: [emerg] host not found in upstream "cost-analyzer-grafana.default.svc" in /etc/nginx/conf.d/default.conf:45

As @AjayTripathy stated, you need to set proxy=false.

Copy link

This issue has been marked as stale because it has been open for 360 days with no activity. Please remove the stale label or comment or this issue will be closed in 5 days.

@github-actions github-actions bot added the stale label Dec 13, 2023
Copy link

This issue was closed because it has been inactive for 365 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

7 participants