+++ This bug was initially created as a clone of Bug #1932401 +++
in my company we use an external load balancer that redirects HTTP traffic to HTTPS.
During an upgrade from 4.6 to 4.7 the cluster-ingress-operator degraded because it couldn't reach the new canary route in openshift-ingress-canary.
I saw that this canary route is a HTTP route. This won't work in our setup.
I manually added edge termination to this route and immediately the upgrade proceeded.
This is a PR that should add 'edge' termination to the canary route:
Thanks and regards,
verified with 4.7.0-0.nightly-2021-03-04-004412 and passed.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.nightly-2021-03-04-004412 True False 88m Cluster version is 4.7.0-0.nightly-2021-03-04-004412
$ oc -n openshift-ingress-canary get route
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
canary canary-openshift-ingress-canary.apps.hongli-47bv.qe.azure.devcluster.openshift.com ingress-canary 8080 edge/Redirect None
$ curl -k https://canary-openshift-ingress-canary.apps.hongli-47bv.qe.azure.devcluster.openshift.com
$ curl -kL http://canary-openshift-ingress-canary.apps.hongli-47bv.qe.azure.devcluster.openshift.com
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 (OpenShift Container Platform 4.7.1 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.