Proposed title of this feature request

Provide support for LoadBalancer services extra settings

What is the nature and description of the request?

When using the LoadBalancer servicePublishingStrategy in a HostedCluster, the configuration for the resulting Service object cannot be tuned. In some scenarios, being able to tune the Service settings may be required.

For example, when using the agent provider (baremetal) and MetalLB to publish the LoadBalancer services we may need to:

• Being able to configure which IPAddressPool is targetted by the LoadBalancer services created by Hypershift. This is required if you have many IPAddressPools available in the management cluster.
• Being able to configure specific IPs to be used by the LoadBalancer services. This is required if you want to setup DNS records for your hosted clusters and need well-known API IPs.

In terms of MetalLB:

• Use case 1 can be accomplished by setting the metallb.universe.tf/address-pool annotation in the service.
• use case 2 can be accomplished by setting the metallb.universe.tf/loadBalancerIPs annotation in the service.

Slack discussion: https://redhat-internal.slack.com/archives/C01C8502FMM/p1704374966517789

Why does the customer need this? (List the business requirements here)

• Being able to leverage more complex MetalLB setups to publish HostedCluster services.

Problem statement and pain points

With the current implementation is not possible to specify specific IPs for the LoadBalancer services. Specifying a different IPAddressPool is not possible either.

List any affected packages or components.

• Hosted Clusters

Similar requests
None