Description of problem: When an IngressController is configured to use an endpoint publishing strategy other than "LoadBalancerService", the ingress operator sets the "LoadBalancerManaged" status condition to "False", with the reason "UnsupportedEndpointPublishingStrategy" to indicate that the ingress operator does not manager a load balancer when the configured endpoint publishing strategy is used. The "UnsupportedEndpointPublishingStrategy" reason is confusing to some users; the word "Unsupported" should be omitted. Version-Release number of selected component (if applicable): 4.3 Steps to Reproduce: 1. Create an IngressController with spec.endpointPublishingStrategy.type set to a value other than "LoadBalancerService". 2. Look at the status of the IngressController created in Step 1. Actual results: The IngressController's status reports "UnsupportedEndpointPublishingStrategy": Message: The endpoint publishing strategy does not support a load balancer Reason: UnsupportedEndpointPublishingStrategy Status: False Type: LoadBalancerManaged Expected results: The IngressController's status should report a less confusing reason, such as "EndpointPublishingStrategyExcludesManagedLoadBalancer".
Verified with 4.5.0-0.nightly-2020-05-04-113741 and the message has been updated as: - lastTransitionTime: "2020-05-06T07:51:47Z" message: The configured endpoint publishing strategy does not include a managed load balancer reason: EndpointPublishingStrategyExcludesManagedLoadBalancer status: "False" type: LoadBalancerManaged
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. https://access.redhat.com/errata/RHBA-2020:2409