You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
When attempting to use the parameter data_stream_template_use_index_patterns_wildcard in the configuration for Elasticsearch (within ClusterOutput), the fluentd configuration inside the pod does not reflect it. The parameter is not added to the configuration despite the latest version of fluent-plugin-elasticsearch (5.4.3) being used in the logging-operator, which supports this parameter.
I suspect that this parameter is missing from the implementation here in both 4.8.0 (my current version) and the latest v5.1.1.
Expected behaviour:
The parameter data_stream_template_use_index_patterns_wildcard should be applied in the fluentd configuration inside the pod when set in Elasticsearch section of ClusterOutput
Steps to reproduce the bug:
Use a ClusterOutput definition that includes the parameter data_stream_template_use_index_patterns_wildcard.
Apply the ClusterOutput configuration to a Kubernetes cluster.
Inspect the fluentd configuration inside the pod.
Observe that the parameter is not added to the fluentd configuration.
Environment details:
Kubernetes version (e.g. v1.15.2): 1.29.4
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): AKS
logging-operator version (e.g. 2.1.1): 4.8.0
Install method (e.g. helm or static manifests): logging-operator installed with helm and ClusterOutput/ClusterFlow with raw helm charts
Describe the bug:
When attempting to use the parameter data_stream_template_use_index_patterns_wildcard in the configuration for Elasticsearch (within ClusterOutput), the fluentd configuration inside the pod does not reflect it. The parameter is not added to the configuration despite the latest version of fluent-plugin-elasticsearch (5.4.3) being used in the logging-operator, which supports this parameter.
I suspect that this parameter is missing from the implementation here in both 4.8.0 (my current version) and the latest v5.1.1.
Expected behaviour:
The parameter
data_stream_template_use_index_patterns_wildcard
should be applied in the fluentd configuration inside the pod when set in Elasticsearch section of ClusterOutputSteps to reproduce the bug:
data_stream_template_use_index_patterns_wildcard
.Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: