-
Notifications
You must be signed in to change notification settings - Fork 252
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
support create LB with existing network/subnet #428
Comments
/assign |
to add more info here:
|
So we'll implement it like I proposed here? |
I would open a PR to fix this, if it's okay :) |
sure, I am too busy recently on other things. so please go ahead and push PR, thanks ~ |
/assign @sbueringer |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Was fixed in #477 /close |
@sbueringer: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
this is a use case at least in my env , you are not authorized to create network/subnet due to restriction on the system ,then you have to reuse existing network to create LB,
however, under current implementation we don't allow this use case, you have to create a new network by using the nodeCIDR setting.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The text was updated successfully, but these errors were encountered: