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

[velero] create prometheusRule only if capabilities are present #481

Merged
merged 2 commits into from
Aug 3, 2023

Conversation

nobbs
Copy link
Contributor

@nobbs nobbs commented Jul 27, 2023

Special notes for your reviewer:

Similar to existing podMonitor and serviceMonitor templates, only create the prometheusRule if the capabilities are present in the cluster (and rules are defined).

Checklist

  • DCO signed
  • Chart Version bumped
  • Variables are documented in the values.yaml or README.md
  • Title of the PR starts with chart name (e.g. [velero])

similar to existing podmonitor and servicemonitor templates, only create
the prometheusRule if the capabilities are present in the cluster (and
rules are defined)

Signed-off-by: Alexej Disterhoft <[email protected]>
Signed-off-by: Alexej Disterhoft <[email protected]>
@qiuming-best qiuming-best merged commit 7857b47 into vmware-tanzu:main Aug 3, 2023
12 checks passed
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.

3 participants