Skip to content

fix(fluentd): keep user forward input transport settings when TLS is enabled - #2382

Open
cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:fix/2380-keep-forward-transport
Open

cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:fix/2380-keep-forward-transport

Conversation

@cvas22

@cvas22 cvas22 commented Nov 17, 2026

Copy link
Copy Markdown

With fluentd.tls.enabled set, CreateSystem swapped forwardInputConfig.transport for a hardcoded block, so any ciphers, version or protocol the user set on the forward listener were silently dropped. It also wrote that block straight into the user's spec object.

Now the operator works on a copy of the forward input config, only forces the cert paths and client_cert_auth, keeps everything else from the user's transport, and falls back to TLSv1_2 only when no version is set. I pulled that logic into a small helper and added a table test for it.

I checked the other TLS spots (fluentd statefulset/configcheck, fluent bit, syslog-ng) and they only mount the secret, so this was the only place with the overwrite.

Fixes #2380

…enabled

Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
@promptless-for-oss

Copy link
Copy Markdown

Promptless documentation updates

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.

Fluentd TLS overwrites user-set forwardInputConfig.transport (ciphers, version and protocol are lost)

2 participants