OKD 4.7: openshift-ingress-operator is degraded if you redirect http to https in external LB

[jomeier]

Hi,

we use an external Load Balancer that redirects all http traffic to https routes.

In OKD 4.7 a new concept was introduced to test the ingress during upgrades with the help of an "openshift-ingress-canary" route.

The operator tests if it gets a HTTP response from the canary route ("hello-openshift"). Because we redirect http traffic to https externally, this route does timeout and the ingress-operator degrades.

If you manually add edge termination to the canary route, everything works again.

openshift/cluster-ingress-operator#555

Greetz,

Josef

[vrutkovs]

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1932649

PR for release-4.7 - openshift/cluster-ingress-operator#558

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale