Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Elasticsearch Pipeline Configuration via Helm Values in Falco Sidekick #748

Open
asfalots opened this issue Sep 26, 2024 · 2 comments · May be fixed by #749
Open

Enable Elasticsearch Pipeline Configuration via Helm Values in Falco Sidekick #748

asfalots opened this issue Sep 26, 2024 · 2 comments · May be fixed by #749
Assignees
Labels

Comments

@asfalots
Copy link

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.

@asfalots asfalots added the kind/feature New feature or request label Sep 26, 2024
@asfalots asfalots linked a pull request Sep 26, 2024 that will close this issue
3 tasks
@Issif
Copy link
Member

Issif commented Sep 26, 2024

Hi,

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.

falcosidekick:
	image:
		tag: latest
	config:
		extraEnv:
			- name: ELASTICSEARCH_PIPELINE
			  value: xxxxx 

I don't have any ETA for now.

@asfalots
Copy link
Author

Thanks,
I missed the extraEnv in the documentation.
At least the PR is ready for 2.30 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants