Bug 1751147 - Authentication operator pods should have proxy env vars
Summary: Authentication operator pods should have proxy env vars
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Standa Laznicka
QA Contact: scheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 09:35 UTC by scheng
Modified: 2019-10-16 06:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:40:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 192 0 'None' closed Bug 1751147: operator: fix typo to get injected with proxy env vars 2020-06-11 17:20:10 UTC
Github openshift cluster-authentication-operator pull 195 0 'None' closed Bug 1751147: Correct ca-bundle filename in terminate on change 2020-06-11 17:20:12 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:02 UTC

Comment 1 Standa Laznicka 2019-09-11 10:35:16 UTC 
In a private discussion, I pointed out that the operator has all of the above.

However, we noticed that the operator does not get injected by the env vars, I'll fix that.
Comment 3 Standa Laznicka 2019-09-13 14:06:55 UTC 
We noticed that the CA changes are not really reflected by the authn operator and that it does not load the proxy CA for route/remote calls.
Comment 4 Michal Fojtik 2019-09-16 13:01:04 UTC 
This is likely broken on https://github.com/openshift/library-go/pull/524 and https://github.com/openshift/cluster-authentication-operator/pull/195
Comment 10 errata-xmlrpc 2019-10-16 06:40:54 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, 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.