This is related to https://issues.redhat.com/browse/RFE-2085 . The request is for a feature to change what IP address our internal DNS records like api-int point at. This would allow customers to send internal cluster traffic to their preferred external loadbalancer.

Scenarios

1. As a cluster admin, I want to send all cluster traffic through my shiny external loadbalancer, including internal cluster traffic.

Previous Work (Optional):

1. We looked into this as part of the external loadbalancer work, but at the time decided not to pursue it because the api-int record is critical to new nodes joining the cluster. However, at that time the intention was that we would remove the internal loadbalancer completely, in which case the default api-int target would stop working. If we left the internal loadbalancer available for bootstrapping nodes but allowed a later override of the records once the node has come up that may be more feasible.