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

Add SSL/TLS settings feature for fluentd output Elasticsearch #418

Closed
phamgiabao1398 opened this issue Oct 10, 2022 · 5 comments · Fixed by #1011
Closed

Add SSL/TLS settings feature for fluentd output Elasticsearch #418

phamgiabao1398 opened this issue Oct 10, 2022 · 5 comments · Fixed by #1011
Labels
good first issue Good for newcomers

Comments

@phamgiabao1398
Copy link

Is your feature request related to a problem? Please describe.

My elasticsearch cluster endpoints using HTTPS with self-sign certificate. I try to use config "ssl_verify false" of fluentd but the crd doesn't support it.

Describe the solution you'd like

Add SSL/TLS settings feature for fluentd output Elasticsearch.

Additional context

No response

@nelsontleidos
Copy link

would love to have "ssl_verify" setting also for development environments.

@allanian
Copy link

+1

@benjaminhuo benjaminhuo added the good first issue Good for newcomers label Feb 14, 2023
@benjaminhuo
Copy link
Member

any contribution to this enhancement is welcome

@husnialhamdani
Copy link

@benjaminhuo, Can I work on this?

@benjaminhuo
Copy link
Member

@benjaminhuo, Can I work on this?
@husnialhamdani
Yes, you're well come to work on this.

antrema added a commit to antrema/fluent-operator that referenced this issue Dec 8, 2023
…uent#418

Signed-off-by: Anthony TREUILLIER <anthony.treuillier@gmail.com>
benjaminhuo added a commit that referenced this issue Dec 11, 2023
fix: Add SSL/TLS settings feature for fluentd output Elasticsearch #418
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants