feat(config): set rule version record limit by default, bump grafana to 11.3.0 #1763
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.
Changes
rule_version_record_limit
to5
by default:alert_rule_version
table would uncontrollably grow to accommodate multiple copies of alert rules;rule_version_record_limit
, which is part ofunified_alerting
section) was introduced to enforce a limit on the rule versions. It is set to0
there by default. To mitigate the behaviour, this PR instructs the operator to set the value to 5 by default;Backwards compatibility
If someone wants to preserve the previous behaviour or postpone initial database cleanup, it's possible to pass:
Fixes: #1639