Current behaviour

Documentation doesn't state that there are any limitations regarding an On-Premise environment. It looks like the DNS Providers are only required for an optional feature in the DNS Policy but if that is not used and RHCL deployed in an On-Premise environment where MetalLB is not installed that means the Gateway needs to be reconfigured as per the Istio documentation. It's unclear if this is a recommended/supported approach from an RHCL perspective.

Expected behaviour

When deploying RHCL in an On-Premise environment it would be helpful to state if there are any limitations with regards to the Gateway and routing capabilities when not using MetalLB and if there are no limitations then simply provide users a link to follow the relevant documentation whether that be Istio, ServiceMesh etc.