bug: Incorrect parameter names in Transport plugin (client_certAuth should be client_cert_auth)

[hs0303kr]

Describe the issue

In the Transport.Params() function (around line 270-273), the following parameters use camelCase instead of snake_case:

if t.ClientCertAuth != nil {
    ps.InsertPairs("client_certAuth", fmt.Sprint(*t.ClientCertAuth))
}

According to Fluentd documentation, these should be:

• client_cert_auth (not client_certAuth)

This causes TLS mutual authentication to fail because Fluentd doesn't recognize the incorrectly named parameters.

To Reproduce

1. Create a Fluentd configuration using the fluent-operator with Transport plugin
2. Set ClientCertAuth: true in the Transport configuration
3. Deploy the configuration
4. Observe that Fluentd doesn't recognize the client_certAuth parameter
5. Check Fluentd logs - the TLS mutual authentication setting is ignored

Expected behavior

The Transport plugin should generate Fluentd configuration parameters using snake_case naming convention as specified in the official Fluentd documentation:

• client_cert_auth for TLS mutual authentication

Your Environment

- Fluent Operator version:v3.5.0
- Container Runtime: 
- Operating system:
- Kernel version:

How did you install fluent operator?

No response

Additional context

Proposed Fix:

if t.ClientCertAuth != nil {
    ps.InsertPairs("client_cert_auth", fmt.Sprint(*t.ClientCertAuth))
}

Reference:

• Fluentd official documentation: https://docs.fluentd.org/input/http#how-to-enable-tls-mutual-authentication
• All Fluentd configuration parameters use snake_case convention

[cw-Guo]

Hi @hs0303kr , would you mind raising a pull request to fix this issue? Thanks.

[hs0303kr]

Hi @hs0303kr , would you mind raising a pull request to fix this issue? Thanks.

Hi! I've created a PR to fix this issue: #1820
Please review when you have a chance. Thanks!