-
Bug
-
Resolution: Done
-
Major
-
4.13, 4.12, 4.11
-
No
-
Proposed
-
False
-
This is a clone of issue OCPBUGS-11442. The following is the description of the original issue:
—
Description of problem:
Currently: Hypershift is squashing any user configured proxy configuration based on this line: https://github.com/openshift/hypershift/blob/main/support/globalconfig/proxy.go#L21-L28, https://github.com/openshift/hypershift/blob/release-4.11/control-plane-operator/hostedclusterconfigoperator/controllers/resources/resources.go#L487-L493. Because of this any user changes to the cluster-wide proxy configuration documented here: https://docs.openshift.com/container-platform/4.12/networking/enable-cluster-wide-proxy.html are squashed and not valid for more than a few seconds. That blocks some functionality in the openshift cluster from working including application builds from the openshift samples provided in the cluster.
Version-Release number of selected component (if applicable):
4.13 4.12 4.11
How reproducible:
100%
Steps to Reproduce:
1. Make a change to the Proxy object in the cluster with kubectl edit proxy cluster 2. Save the change 3. Wait a few seconds
Actual results:
HostedClusterConfig operator will go in and squash the value
Expected results:
The value the user provides remains in the configuration and is not squashed to an empty value
Additional info:
- blocks
-
OCPBUGS-11608 User configured In-cluster proxy configuration squashed in hypershift
- Closed
- clones
-
OCPBUGS-11442 User configured In-cluster proxy configuration squashed in hypershift
- Closed
- is blocked by
-
OCPBUGS-11606 User configured In-cluster proxy configuration squashed in hypershift
- Closed
- links to