Skip to content

fix(fluent-bit): Listen on IPv6+IPv4#663

Closed
jplitza wants to merge 1 commit into
fluent:mainfrom
jplitza:patch-1
Closed

fix(fluent-bit): Listen on IPv6+IPv4#663
jplitza wants to merge 1 commit into
fluent:mainfrom
jplitza:patch-1

Conversation

@jplitza
Copy link
Copy Markdown

@jplitza jplitza commented Dec 4, 2025

This fixes #355

This fixes #355

Signed-off-by: Jan-Philipp Litza <jplitza@users.noreply.github.com>
Copy link
Copy Markdown

@lilioid lilioid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can confirm that this works. A fluent-bit process started with http_listen: "::" listens on both IPv4 (so is compatible to the old behavior) as well as IPv6.

I would like to see this merged as well :)

@genestack-okunitsyn
Copy link
Copy Markdown

It would be great to have it merged, very helpful!

Copy link
Copy Markdown
Collaborator

@stevehipwell stevehipwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @jplitza, please could you make sure you follow the contribution guide.

RE this PR, if you want to make a major change like this you 100% need to open an issue to discuss it (I can't see this change being approved in this state). The current chart will allow you to override http_listen by setting config.service, if you want to make it more customizable you could add a new value but you'd also need to check if 0.0.0.0 is hardcoded anywhere else in the chart and keep that in sync.

If you look at the fluent-bit-aggregator & fluent-bit-collector charts you'll see that this can already be set via config.service.http_listen. I'd strongly recommend that you switch over to one of these charts.

@jplitza
Copy link
Copy Markdown
Author

jplitza commented May 18, 2026

please could you make sure you follow the contribution guide.

I did at the time of opening the PR.

a major change like this

How is this a major change? It is backwards compatible, because :: accepts IPv4 as well as IPv6.

but you'd also need to check if 0.0.0.0 is hardcoded anywhere else in the chart

It isn't. (Okay, I should have changed the readme as well.)

I'd strongly recommend that you switch over to one of these charts.

That's what we did by now. But again, when I opened the PR, that chart didn't exist. So...

I can't see this change being approved in this state

I'm closing this.

@jplitza jplitza closed this May 18, 2026
@jplitza jplitza deleted the patch-1 branch May 18, 2026 07:11
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.

Fluentbit Liveness/Readiness Probes failed helm chart version 0.29.0

4 participants