Bug 1870289 - Put ClusterLogForwarer into cluster scope
Summary: Put ClusterLogForwarer into cluster scope
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.6.0
Assignee: Alan Conway
QA Contact: Qiaoling Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-19 16:47 UTC by Alan Conway
Modified: 2020-10-27 15:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 15:09:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 580 0 None closed Bug 1870289: LOG-755: Make ClusterLogForwarder cluster scoped 2020-10-16 13:21:31 UTC
Red Hat Product Errata RHBA-2020:4198 0 None None None 2020-10-27 15:10:11 UTC

Description Alan Conway 2020-08-19 16:47:21 UTC 
Description of problem:

ClusterLogForwarder is presently a namespace-scoped resource.
It should to be cluster scoped as it controls log forwarding for the whole cluster.
Comment 1 Alan Conway 2020-08-19 17:46:38 UTC 
PR is https://github.com/openshift/cluster-logging-operator/pull/580
Comment 4 Qiaoling Tang 2020-08-24 08:47:45 UTC 
Verified with clusterlogging.4.6.0-202008202200.p0

$ oc api-resources |grep logging
NAME                                  SHORTNAMES       APIGROUP                              NAMESPACED   KIND
clusterlogforwarders                  clf              logging.openshift.io                  false        ClusterLogForwarder
Comment 6 errata-xmlrpc 2020-10-27 15:09:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6.1 extras update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4198
Note You need to log in before you can comment on or make changes to this bug.