Split apiserver availability rule groups #1032
Draft
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.
Split the apiserver availability rules into two rule groups for async processing. This makes the rule groups less heavy without greatly impacting the data quality.
Some other improvements:
code
rule split. Since these rules are sequential in one rule group it doesn't really improve performance. It also confuses the Prometheus Operator admission controller. Removing the regexp match also reduces the load on Prometheus.verb
regexp match so we also eliminate this regexp match. This also allows for all verbs to be included in this aggregation.