Description of problem:
a https readiness endpoint is considered invalid if httpsProxy uses a http url scheme. httpsProxy supports http and https url schemes. It's common to use an http url scheme for an https proxy. Cluster Network Operator should consider either httpsProxy url scheme valid when using a readiness endpoint with an https scheme.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a cluster without proxy enabled, but with additionalTrustBundle configured with your proxy's trust bundle.
2. Enable proxy by configuring a http url scheme for httpsProxy and a readiness endpoint with a https scheme. For example:
$ oc get proxy/cluster -o yaml
3. View the proxy and notice that status is not being set.
oc get proxy/cluster -o yaml
4. View the network operator
oc get clusteroperator/network -o yaml
message: 'The configuration is invalid for proxy ''cluster'' (readinessEndpoint
probe failed for endpoint ''https://www.google.com'': endpoint ''https://www.google.com''requires a `https` proxy scheme). Use ''oc edit proxy.config.openshift.io cluster'' to fix.'
cluster-network-operator to accept the configuration and write spec > status.
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.