Cleanup of bindings for PrometheusRules in prometheus#8024
Cleanup of bindings for PrometheusRules in prometheus#8024simonpasquier merged 4 commits intoprometheus-operator:mainfrom
Conversation
|
@simonpasquier review and merge! is failing i dont think it belong to my code changes |
simonpasquier
left a comment
There was a problem hiding this comment.
I'm not sure to understand why we need a custom CleanupPrometheusRuleBindings() for rules?
|
@simonpasquier we are using different value of key for promRule k := fmt.Sprintf("%v-%v-%v.yaml", promRule.Namespace, promRule.Name, promRule.UID) |
|
Thanks for the clarification. I'd prefer to avoid a special case for PrometheusRule. |
…esourcesStatus and configResStatusCleanup
…ings in PrometheusRules
…in updateConfigResourcesStatus
|
@simonpasquier PTAL |
Description
Cleanup of bindings for PrometheusRules in prometheus
Closes: #7924
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.