-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Calico on IPV6 fails on connectivity to Datastore #2758
Comments
From the error message I would guess that kube-proxy perhaps isn't working correctly or isn't running in IPv6 mode. You should try doing a |
I am facing this same issue. and in kube-proxy logs i am not seeing anything strange also.
Here are my kube-proxy logs
|
Did you try the curl command I suggested? (You'll need to make sure you're using the k8s-apiserver service address) |
I am getting "curl: (7) Couldn't connect to server". |
@skyfirst93 that indicates an issue with reaching the apiserver from the host, if that does not work then node will not be able to reach it either. You should try accessing the apiserver directly (not using the service address), basically you'll need to figure out why accessing the apiserver through the service is not working. |
@skyfirst93 are you able to solve the issue ? I am also getting the similar error. |
i Could not. still stuck |
@skyfirst93 My issue is resolved after adding default gw in the node. Add default gw and try the curl command to access your API service IP address from your host. Unless that is not accessable, your cluster wont be up. My node ip is 2001:db8:0:f101::2, I added a dummy route as shown below, and then tried curl command which worked me. if you use ipvs instead of iptables, I could see it is working without any default route as ipvsadm is adding the following rule. fd20::1 is my clusterIP TCP [fd20::1]:443 rr |
Thanks @etavene setting the dummy route worked for me |
Hello , I am trying to run K8S with calico on an IPV6 environment that does not have any IPV4 interface.
currently I am unable to start and I kepp failing on calico-node errors:
2019-07-28 12:35:43.076 [INFO][8] startup.go 331: Hit error connecting to datastore - retry error=Get https://[fd20::4001]:443/api/v1/nodes/foo: dial tcp [fd20::4001]:443: connect: network is unreachable
this is the calico.yaml file I was using :
I am running on centos 7.4 machine on premise as AWS won't allow IPV6 only.
I am using calico 3.8.0
any help would be much appriciated
The text was updated successfully, but these errors were encountered: