add configurable 'job_selectors' and 'cluster_selectors' #935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
Similiar to grafana/cortex-jsonnet#319 in cortex, Replaces hard-coded usage of [namespace, job] or [namespace, cluster] in alerts and recording rules to support different configurations of cluster and job unique identifier labels.
I generated the existing alerts/rules in
yamls/
folder and the only differences I see are recent changes toyamls/alerts.yml
that haven't been syncedWhich issue(s) this PR fixes:
N/A
Checklist
- [ ] Tests updated- [ ] Documentation addedCHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]