Usage of publish parameter in the install-config.yaml file while deploying OpenShift Container Platform 4

Issue

• Installation failing with the use of publish: Internal parameter in the install-config over on-premise platforms (platforms that doesn't possess the capabilities to create internal loadbalancer services like vSphere, OSP, RHV).
• Ingress cluster operator is degraded due to the pendingstate of router loadbalancer-type service. Due to the unavailability of ingress operator, other operators like authentication, console reports degraded status.

$ oc get service -n openshift-ingress
NAME                              TYPE           CLUSTER-IP     EXTERNAL-IP       PORT(S)                 AGE
service/router-default            LoadBalancer   10.5.5.5      <pending>     80:32613/TCP,443:31865/TCP   4h
service/router-internal-default   ClusterIP      100.10.5.5     <none>        80/TCP,443/TCP,1936/TCP      4h
===============================================================================================================================
Issue          : Degraded
    Reason         : IngressControllersDegraded
    Message        : Some ingresscontrollers are degraded: ingresscontroller "default" is degraded: DegradedConditions: One or more other status conditions indicate a degraded state: LoadBalancerReady=False (LoadBalancerPending: The LoadBalancer service is pending)

• The openshift-installer should only accept publish: Internal parameter for platforms with the capabilities to create an internal loadbalancer service automatically.