[occm] Should internal-network-name have an impact on the internalIPs picked up for LoadBalancer Members?

[pabclsn]

[occm] internal-network-name for LoadBalancers

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature

When a Loadbalancer is created with the OCCM. The OCCM chose the default InternalIP of a worker node, but It would be nice to have the same behavior as internal-network-name because a worker node can have multiple interfaces, in my case, the loadbalancer is not in the same subnet as my main InternalIP, and I cannot connect my InteralIP subnet to a router.

Environment:

• OCCM version: latest
• OpenStack version: 2024.2
• Others:

[zetaab]

@pabclsn is this related to #2718 ?

[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