[prometheus-operator] fixed hardcoded label for grafana servicemonitor

[Morriz]

Now each grafana instance can have it's own servicemonitor. Fixes #23513

• DCO signed
• Chart Version bumped

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Morriz
To complete the pull request process, please assign gianrubio
You can assign the PR to them by writing /assign @gianrubio in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• stable/prometheus-operator/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @Morriz. Thanks for your PR.

I'm waiting for a helm member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Morriz]

/assign @gianrubio

[Morriz]

Signed-off-by: [email protected]

[scottrigby]

/hold

Let’s hold PRs to prometheus-operator for a short time until prometheus-community/community#28 (comment) is resolved. If you want to help with that effort, to test etc, that would be great!

[scottrigby]

@Morriz as a user/contributor, would you mind helping to review and test this PR? prometheus-community/helm-charts#1

No need to reply here. If you can, please just reply and help there. It would help this process move along faster. Thanks!

[Morriz]

@scottrigby I am replying here though, as I am still not a maintainer, and can't add myself as reviewer yet. But I would like to!

[scottrigby]

@Morriz hi 👋 I created this issue to discuss adding additional chart maintainers for the new repo. This will have to be a conversation with current maintainers and prom devs.

prometheus-community/helm-charts#21

PS, Generally what is good to see before adding a user as a maintainer of a chart is a history of contribution, willingness to read best practice guides, and be generally helpful witha chart (including help testing and reviewing other pull requests), etc. Hope that helps 🙂

[scottrigby]

@Morriz another thing that would be very helpful at this point is testing this PR: prometheus-community/helm-charts#1

See these comments:

• What's needed to test: [prometheus-operator] Rename to kube-prometheus-stack prometheus-community/helm-charts#1 (comment)
• How to test: [prometheus-operator] Rename to kube-prometheus-stack prometheus-community/helm-charts#1 (comment) (explains why you will need to make one temporary manual edit to requirements.yaml)

User testing is not required but it will help give higher confidence that everything has been addressed properly in the renaming PR.

[scottrigby]

🚧 This chart is now deprecated.

Further development has moved to prometheus-community/helm-charts. The chart has been renamed kube-prometheus-stack to more clearly reflect that it installs the kube-prometheus project stack, within which Prometheus Operator is only one component.

If applicable, please re-open this PR there. Thanks!