This repository has been archived by the owner on Apr 25, 2021. It is now read-only.
Helm: add support for secret rules and config #33
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.
Hi there!
This PR adds support for loading the Elastalert configuration and/or rules via Kubernetes secrets.
Three new variables were added to
values.yaml
:secretConfigName
: name of the secret which holds the Elastalert config. Note: this will overwrite the generated config and must contain a full working configsecretRulesName
: name of the secret which holds the Elastalert rules. Note: this will overwrite the generated rules and must contain all rules in separate data fieldssecretRulesList
: a list of rules to enable from the secretIt's worth mentioning that it was not possible to load a single secret with multiple rules separated by
---
, it threw the error below. This is whysecretRulesList
was needed.I have updated the documentation and provided examples of working secrets in the
values.yaml
.Thanks!