Description of problem: Ticket to track changes around changing the LoadBalancer Scope from immutable to mutable to support a patch of the IngressController CR. This BZ is for the backport to 4.6.z. Additional info: Ref: https://issues.redhat.com/browse/NE-172 PR: https://github.com/openshift/cluster-ingress-operator/pull/472
*** Bug 1892447 has been marked as a duplicate of this bug. ***
We'll try to get this backport merged in the upcoming sprint.
verified with a cluster (4.6.0-0.ci.test-2020-11-16-084740-ci-ln-qmbvd9t) launched by cluster-bot and passed. # oc -n openshift-ingress-operator patch ingresscontroller/default -p '{"spec":{"endpointPublishingStrategy":{"loadBalancer":{"scope":"Internal"}}}}' --type=merge ingresscontroller.operator.openshift.io/default patched
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.6.6 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. https://access.redhat.com/errata/RHBA-2020:5115
This was a feature backport and I don't believe we should ever set feature backports at high severity. Feature backports go in only once we've cleared the critical period immediately after GA and have enabled upgrades for everyone. Backporting this feature when we did has halted efforts to promote the upgrade.