Elon Cheng

hi, @muhammedsoner . Thank you for your feedback. This issue has been fixed, please see https://github.com/fluent/fluentbit-operator/pull/160.

It looks like this in terms of error messages.https://github.com/fluent/fluent-bit/issues/4103 Can you show me the configuration of the Output plug-in?

Maybe you can modify the Input plugin. The input.spec.tail.path property specifies the log collection address

Also, you can modify fluentbit.spec.containerLogRealPath to modify Container log path. Here is code https://github.com/wenchajun/fluentbit-operator/blob/master/api/fluentbitoperator/v1alpha2/fluentbit_types.go#L36

This looks like there is a problem with validation. As you can see from the error message, the information about the user has been written to the configuration file.

In my opinion, you can check this in two ways. First you can start by looking at the secret fluentd-config to check that the passwd is written correctly. Then you...

The configuration file should not be placed in the deployment, it is the output crd. Here https://github.com/fluent/fluent-operator/blob/master/apis/fluentd/v1alpha1/plugins/output/es.go#L26.

One more thing, fluent-operator will generate the appropriate fluentd config file based on the crd you write and then mount it on `fluentd`, so if that doesn't work you can...

You can try creating two secrets and see if its `passwd` is the desired value.

What is your version of Kubesphere? An adaptation for containerd is available in kubespherev3.2.Each change in ClusterConfiguration will cause the ks-Installer to be reinstalled, but the original configuration will be...