You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Motivation
The current Falco Sidekick Helm chart does not support configuring Elasticsearch pipeline settings in the values.yaml file, even though this feature is already supported in Falco (as seen in the documentation). The missing configuration in the secret.yaml prevents the seamless integration of Elasticsearch pipeline settings.
Feature
Add the ability to configure Elasticsearch pipeline settings in the values.yaml and secret.yaml files of the Falco Sidekick Helm chart.
Alternatives
Currently, the only workaround is to manually edit the secret.yaml file after deploying the chart, which is not ideal and prevent using gitops approach like with ArgoCD
Additional context
A pull request has been prepared and will be submitted to address this feature request.
The text was updated successfully, but these errors were encountered:
The pipeline has been integrated in the master branch, but not released in a tagged version yet (it will be in the 2.30.0), this is why it's not available in the Helm values.
It's possible anyway to use it, by changing the image tag to latest and by setting extraEnv.
Motivation
The current Falco Sidekick Helm chart does not support configuring Elasticsearch pipeline settings in the
values.yaml
file, even though this feature is already supported in Falco (as seen in the documentation). The missing configuration in thesecret.yaml
prevents the seamless integration of Elasticsearch pipeline settings.Feature
Add the ability to configure Elasticsearch pipeline settings in the
values.yaml
andsecret.yaml
files of the Falco Sidekick Helm chart.Alternatives
Currently, the only workaround is to manually edit the
secret.yaml
file after deploying the chart, which is not ideal and prevent using gitops approach like with ArgoCDAdditional context
A pull request has been prepared and will be submitted to address this feature request.
The text was updated successfully, but these errors were encountered: