This is a feature request. Sorry, I couldn't find anywhere else to file it. Our team can also potentially implement this feature, so really we're looking for design input before possibly submitting a PR.

User story:

As a user of on-prem OpenShift, I need to manage DNS for my OpenShift cluster manually. I can already specify an IP address for the API server, but I cannot do this for Ingress. This means that I have to:

• Manually create the API endpoint IP
• Add DNS for the API endpoint
• Create the cluster
• Discover the created Ingress endpoint
• Add DNS for the Ingress endpoint

I would like to simplify this workflow to:

• Manually create the API and Ingress endpoint IPs
• Add DNS for the API and Ingress endpoints
• Create the cluster

Implementation suggestion:

Our specific target is OpenStack. We could add `OpenStackLoadBalancerParameters` to `ProviderLoadBalancerParameters`, but the parameter we would be adding is 'loadBalancerIP`. This isn't OpenStack-specific. For example, it would be equally applicable to users of either OpenStack's built-in Octavia loadbalancer, or MetalLB, both of which may reasonably be deployed on OpenStack.

I suggest adding an optional LoadBalancerIP to LoadBalancerStrategy here: https://github.com/openshift/cluster-ingress-operator/blob/8252ac492c04d161fbcf60ef82af2989c99f4a9d/vendor/github.com/openshift/api/operator/v1/types_ingress.go#L395-L440

This would be used to pre-populate spec.loadBalancerIP when creating the Service for the default router.