You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
[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:
The text was updated successfully, but these errors were encountered: