Bug 1929413 - ClusterLogForwarder does not honor Output Secret Spec
Summary: ClusterLogForwarder does not honor Output Secret Spec
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard: logging-core
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 20:22 UTC by Jeff Cantrill
Modified: 2021-02-19 15:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-19 15:26:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Cantrill 2021-02-16 20:22:48 UTC 
Description of problem: 
The ClusterLogForwarder allow a user to specify the name of a secret to use when connecting to a given output. The conf generation code ignores the secret name and assumes a secret exists that is names the same as the output


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

CLF generates configuration to utilize the spec'd secret name


Additional info:
Comment 1 Jeff Cantrill 2021-02-16 20:51:28 UTC 
5.0 fixed here https://github.com/openshift/cluster-logging-operator/pull/895
Comment 3 Jeff Cantrill 2021-02-19 15:26:18 UTC 
Closing NOTABUG as change is not required
Note You need to log in before you can comment on or make changes to this bug.