keepalived implementation in VMware vSphere doing UPI installation method should be optional

1. Proposed title of this feature request
keepalived implementation in VMware vSphere doing UPI installation method should be optional

2. What is the nature and description of the request?
keepalived has been implemented to achieve IPI installation method on VMware vSphere as generally VMWare does not provide Load-Balancer capabilities. While this is valid, many customer installing on VMware vSphere using UPI has proper Load-Balancer technology available and would rather use that, than keepalived. It's therefore requested to make the deployment of keepalived optional when doing UPI on VMware vSphere as enterprise customers tend to have enterprise ready services available that provide the required functionality. Also keepalived is not something appreciated in enterprise networks, which is why customers would rather provide enterprise Load-Balancer by them self when providing their own infrastructure (which is the aim of UPI).

3. Why does the customer need this? (List the business requirements here)
With UPI Installation method, the customer is expected to provide the infrastructure using it's own methodology. Being forced to rely on keepalived can cause dissatisfaction and in large scale environments can also become a bottleneck. This is why customers prefer to really provide their own infrastructure, skip the deployment/configuration of keepalived and manage that part of the infrastructure them-self.

Hence having an option to disable/prevent the installation/deployment of keepalived on these platforms would be appreciated.

4. List any affected packages or components.
OpenShift Container Platform - Installer
vSphere Cloud Provider