Load balancers are not zone redundant and can't be configured as such

[jhixson74]

/kind bug

What steps did you take and what happened:
CAPZ does not expose availability zones in the LoadBalancerSpec. I am using CAPZ to provision a cluster by filling out an AzureClusterSpec. The cluster is provisioned correctly. VM's are zone redundant. Internal API load balancer is not zone redundant.

What did you expect to happen:
I expect the internal load balancer to be zone redundant. I expect to be able to configure this via the LoadBalancerSpec struct.

Anything else you would like to add:
Is this intentional? Are there any plans to support this in the future?

Environment:

• Red Hat Open Shift 4.20
• cluster-api-provider-azure version: v1.19.3
• Kubernetes version: k8s.io/client-go v0.32.1
• OS: Fedora 42

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale