Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pabclsn opened this issue Oct 22, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@pabclsn
Copy link

pabclsn commented Oct 22, 2024

[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:
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 22, 2024
@zetaab
Copy link
Member

zetaab commented Nov 18, 2024

@pabclsn is this related to #2718 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants