-
Notifications
You must be signed in to change notification settings - Fork 60
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
Cannot connect to control plane on IPv6 when IPv4 is disabled. #899
Comments
I looked through the code and it seems that this would have to be an option on the HetznerCluster object as that's what controls the API server endpoint URI. So something along the lines of controlPlaneEndpoint:
host: ""
port: 443
ipv6Only: true |
The controlPlaneEndpoint doesn't come from us it's imported. But in general you can solve this problem by using a domain for the |
Alright, that would work. Also, just found out the LB doesn't support IPv6-only targets for some reason. So using a private network or creating our own LB is the only option for now I suppose. Thank you |
/kind bug
What steps did you take and what happened:
Create a cluster with
enableIPv4
false
andenableIPv6
totrue
.Results in WaitingForNodeRef on those machines.
What did you expect to happen:
The nodes to join the cluster.
Anything else you would like to add:
It seems to be using the IPv4 address of the LB (which can't be disabled), instead of the IPv6 one. The machines don't have IPv4 access.
I believe it should only use the LB IPv4 when enableIPv4 is set to true. If enableIPv4 is explicitly false and enableIPv6 is true, it should use the IPv6 address of the LB.
Environment:
kubectl version
) v1.25.5/etc/os-release
): Ubuntu 22.04.1 LTSThe text was updated successfully, but these errors were encountered: