Loading...

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: Logging 5.5.6
Affects Version/s: Logging 5.5.z
Component/s: Log Collection
Labels:

Blocked:
False
Blocked Reason:
None
Ready:
False
Docs QE Status:
NEW
QE Status:
VERIFIED
Release Note Text:

Hide
Before this change the spec for outputDefaults of the ClusterLogForwarder would apply the settings to every declared Elasticsearch output type. This change corrects the behavior to match the enhancement specification where the setting specifically applies to the "default" managed Elasticsearch store.

Show
Before this change the spec for outputDefaults of the ClusterLogForwarder would apply the settings to every declared Elasticsearch output type. This change corrects the behavior to match the enhancement specification where the setting specifically applies to the "default" managed Elasticsearch store.

Sprint:
Log Collection - Sprint 228, Log Collection - Sprint 229, Log Collection - Sprint 230

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

OutputDefault is being applied to ANY ES output, rather than only apply to our default ES offering. There is a similar functionality available for a defined instance of an Elasticsearch output, but the defaults should not "merge" into the customer defined instance.

The documentation needs to be updated to correct this as well:
https://issues.redhat.com/browse/RHDEVDOCS-4549

Notes:

https://github.com/openshift/cluster-logging-operator/pull/1668
https://github.com/openshift/cluster-logging-operator/blob/master/internal/k8shandler/forwarding.go#L41

clones

LOG-3228 OutputDefaults is being applied to any ES output rather than only default