Bug 1988197 - openshift-authentication-operator POD is ignoring the noproxy setting and sending traffic to the proxy
Summary: openshift-authentication-operator POD is ignoring the noproxy setting and sen...
Keywords:
Status: CLOSED DUPLICATE of bug 1982738
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oauth-proxy
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Standa Laznicka
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-30 03:41 UTC by Vincent Lours
Modified: 2021-07-30 07:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-30 07:23:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vincent Lours 2021-07-30 03:41:36 UTC 
Description of problem:
While the proxy setting is defined correctly in the proxy/cluster object, the openshift-authentication-operator POD is ignoring it, and send some request to the proxy server.

This is the only URI hitting the proxy: https://oauth-openshift.apps.<domain>

The behaviour is observed from the proxy logs and confirmed from a Tcpdump packet capture.

Based on the proxy events, this may be related to the liveness of the POD trying to check the `healthz` state of the authentication URI.


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

The cluster has been updated to 4.7.19 (upgraded throughout 4.6.36). This behaviour was not seen in the previous version: 4.5.30


How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.

Actual results:
The operator is sending traffic to the proxy.

Expected results:
No traffic to the proxy


Additional info:
Comment 2 Standa Laznicka 2021-07-30 07:23:30 UTC 

*** This bug has been marked as a duplicate of bug 1982738 ***
Note You need to log in before you can comment on or make changes to this bug.