fluent-bit
fluent-bit copied to clipboard
fluent
Support TLS on Forward Input plugin
According to https://docs.fluentbit.io/manual/administration/security TLS is only supported in output plugins. I will be great also to have support for input plugins. Mostly because we prefer to use fluent-bit over fluentd as it is simpler and has a lower footprint.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Hello, I think I know why input plugins do not support TLS.
Perhaps, I can deploy flb behand a nginx server, I just need to config my nginx server to support TLS, and let nginx forward traffic to flb.
Hello, I think I know why input plugins do not support TLS.
Why that will be? fluentd supports TLS for this.
Is the desired design that folks use a service mesh to handle the TLS between pods? Either way, the ticket is still relevant!
That feeling when you build your first fluentbit forward setup and when you're almost done, you find out, when building the receiving end, that it cannot serve a TLS endpoint (especially weird since it receives a secret) and you find a github issue older than a year without at least a response of the maintainer about why such feature that anyone with common sense would expect is simply not there. ¯\(ツ)/¯
I want to use fluentbit to stream syslog to my elasticsearch cluster in a secure fashion. Since the es output of fluentbit doesn't have the option (like in the fluentd one) to specify multiple output hosts, the documentation points you to the upstream forwarder approach. Fine with that, but please at least mention there's (apparently?) no way you can build this securely. :(
Is the desired design that folks use a service mesh to handle the TLS between pods?
My motivation for preferring fluentbit over other solutions is its small footprint. If I need a proxy or something like that in addition, I can just as well go with fluentd, I guess.
After problems with fluentd and seeing old same issues without any answer there I thought maybe fluent-bit is better, but it does not seem to. Is fluentd not maintained anymore?
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
I don't think it's possible at the moment but it will be in 2.0 (which will also include TLS support for input plugins)
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
Yes, it came out in 2.0 and I have fixed a few issues that were identified in latest version (I think it came out yesterday).
Per https://docs.fluentbit.io/manual/administration/transport-security bluent-bit 2.0 input tls just supports MQTT, TCP, HTTP and OpenTelemetry, no forward
But fluentd supports it https://docs.fluentd.org/input/forward#how-to-enable-tls-encryption
It seems like there's an error in the documentation. The forward input plugin has TLS support in Fluent-bit 2.0+