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

[kube-prometheus-stack] small rewrite of kube-prometheus-stack/README.md for easier understanding #4401

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dominik-ba
Copy link

@dominik-ba dominik-ba commented Mar 27, 2024

What this PR does / why we need it

This is a documentation / Readme change only
I personally think this little change of the intro improves the readme for easier understanding what is happening when one deploys this chart. Adding the operator only as a very last comment to me was always confusing because after all its not only a stack that deploy individual instances but uses the operator at its core. Happy to discuss.

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

  • fixes #

Special notes for your reviewer

Checklist

  • [x ] DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

Signed-off-by: Dominik Bartsch <7559494+dominik-ba@users.noreply.github.com>
@jkroepke
Copy link
Member

Hi, sound great to me.

Please highlight, that Prometheus rules and dashboard are coming from https://github.com/prometheus-operator/kube-prometheus.

And also please bump the chart version.

@dominik-ba dominik-ba changed the title small rewrite of kube-prometheus-stack/README.md for easier understanding [kube-prometheus-stack] small rewrite of kube-prometheus-stack/README.md for easier understanding Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants