Skip to content

fix(loki): preserve default alert rules with custom files#3995

Open
Yaguang Tang (yaguangtang) wants to merge 1 commit into
mainfrom
codex/loki-custom-rule-merge
Open

fix(loki): preserve default alert rules with custom files#3995
Yaguang Tang (yaguangtang) wants to merge 1 commit into
mainfrom
codex/loki-custom-rule-merge

Conversation

@yaguangtang

Copy link
Copy Markdown
Member

Summary

  • preserve the default Loki alert rules when custom rule files are provided
  • add loki_alert_rule_files as the supported way to append extra Loki rule files
  • add a Loki role test and a release note for the new rule file behavior

Testing

  • go test ./roles/loki -count=1

@yaguangtang Yaguang Tang (yaguangtang) force-pushed the codex/loki-custom-rule-merge branch 2 times, most recently from 8472d96 to 849312e Compare May 26, 2026 15:40
Move the default Loki alert rules out of the generic loki_helm_values
merge path and build the loki-alerting-rules ConfigMap explicitly from
dedicated rule-file variables.

This keeps the Atmosphere-provided rules in place while letting operators
add extra rule files through loki_alert_rule_files without replacing the
default ConfigMap object or other list-valued Helm settings.

Add a Loki role test covering the default rule file and custom rule file
coexistence, and include a release note describing the new custom rule
file behavior.

Signed-off-by: Yaguang Tang <yaguang.tang@vexxhost.com>
@yaguangtang Yaguang Tang (yaguangtang) force-pushed the codex/loki-custom-rule-merge branch from 849312e to 145e0dc Compare May 27, 2026 13:30
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.

1 participant