-
Notifications
You must be signed in to change notification settings - Fork 431
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
Internal LB not created for IPv6 #952
Comments
/assign |
/milestone v0.4.6 |
@CecileRobertMichon: The provided milestone is not valid for this repository. Milestones in this repository: [ Use 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. |
/milestone v0.4.10 |
/close |
@CecileRobertMichon: 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. |
The internal LB is actually not being used for anything right now for ipv4 clusters (see #696). I plan to start using it as part of #486, but there is a bug for which a fix is currently being rolled out where check IP availability doesn't work when the vnet has an IPv6 address range, so I disabled the internal LB in the meantime for ipv6 until we can rationalize this stuff in #486 once the fix is rolled out completely (I already have a POC in my local branch).
Originally posted by @CecileRobertMichon in #646 (comment)
The text was updated successfully, but these errors were encountered: