Some customers are restricted to use only some external ports (443, 80) to the external load balancers in their datacenters (due to firewall and anti-DoS rules).

More than public cloud installations, where it is more easy to add some extra policies, this applies to private ones (VMWare, Bare Metal, etc).


There are other bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1663453
https://bugzilla.redhat.com/show_bug.cgi?id=1686139

Close as WONTFIX, but I guess they are related to use 443 in the container, not exposing it through the LB.

The idea will be to be able to expose API port in 6443 in the instances, and exposing it through 443.


Version: 4.1.x
How reproducible: Always.


Actual usage:
oc login https://api.cluster.base:6443

Expected usage:
oc login https://api.cluster.base

It is a blocker to OCP 4.x adoption in restricted environments (public sector).