-
Epic
-
Resolution: Done
-
Normal
-
None
-
Remove Legacy Forwarding
-
2
-
False
-
False
-
NEW
-
Done
-
NEW
-
0% To Do, 0% In Progress, 100% Done
-
In OpenShift Logging 5.3, the legacy configuration mechanism for log forwarding is removed: You cannot forward logs using the legacy Fluentd method and legacy Syslog method. Use the standard log forwarding methods instead.
Summary
In OpenShift 4.6, we finally released the new Log Forwarding API as GA and at the same time deprecated the legacy mechanism (ConfigMaps via Fluentd). We did not remove it immediately to give time for customers to 1) look at potential gaps and 2) give them enough time to move to the new API-based approach.
This ticket contains work to remove the legacy mechanism from our code and only support the new API moving beyond this ticket.
Acceptance Criteria
- CLO should no longer support legacy forwarding as described by documentation
- CLO generation code should no longer support legacy forwarding
- CLO tests are no longer executed by CI
Notes
- Ref: https://docs.openshift.com/container-platform/4.6/logging/cluster-logging-external.html#cluster-logging-collector-legacy-fluentd_cluster-logging-external
- https://docs.openshift.com/container-platform/4.6/logging/cluster-logging-external.html#cluster-logging-collector-legacy-syslog_cluster-logging-external
- is documented by
-
RHDEVDOCS-2681 Document "Remove legacy configuration mechanism for log forwarding from RHOL"
-
- Closed
-
