Bug 1805168
Summary: | openshift-controller-manager makes direct http requests even when a proxy is set | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Christophe Fergeau <cfergeau> |
Component: | openshift-controller-manager | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.0 | CC: | aos-bugs, gmontero, mfojtik, prkumar |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | devex | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: the image stream signature controller in the openshift controller manager deployment makes direct http/https requests to registries accessed by imagestreams, and the openshift controller manager was not being set up to deal with global proxies
Consequence: global proxies were not properly utilized by the image signature controller in the openshift controller manager
Fix: the openshift controller manager operator now seeds the openshift controller manager with the proxy environment variables and ca certificates needed to properly communicate with openshift global proxy
Result: the image signature controller now leverages openshift global proxies correctly when contacting external registries
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:16:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christophe Fergeau
2020-02-20 12:11:31 UTC
For what it's worth, I tested this on 4.4, and I can still reproduce the issue. This is expected as the fix was not backported to 4.4 and is only available in 4.5+. Yep, at this time the fix has not been backported to any releases prior to 4.5. 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-2020:2409 |