-
Notifications
You must be signed in to change notification settings - Fork 295
Calico enabled cluster produces non-functional network? #289
Comments
Hello @redbaron Note, that we hadn't seen this problem before. And this is with us keeping all of our cluster.yaml configurations/settings the same as we've used in all previous releases (up to and including rc.5), using cluster.yaml from git and merging with the latest versions default file and the new config options, etc. As noted in the below comments, that gist/summary is that we seem to have hit some (in our case internet) connectivity issues with the current pre-release version 0.9.3. Perhaps unrelated to Calico specifically, but if we just roll-back to rc.5 (and implement our cloud-init hostname fix for our custom DHCP option set), we again get a working and deployable cluster. Below are a couple of my comments that describe our observed symptoms/issues with the latest 0.9.3 pre-release (in our existing VPC with internal private subnets using NAT): |
Hi @heschlie, could you share your insight on this? 🙇 |
What seems to be happening is that both when using Overall it is not a kube-aws problem, upstream issue was opened https://github.com/projectcalico/k8s-policy/issues/67 |
This is preliminary bugreport in case somebody pulling hair like me , maybe we can join forces.
Long story short - pods on worker nodes can't reach apiserver.
Symptomps:
Flanneld can't find route to LOCAL ip address:
Weird routing table inside pod:
should it be
169.254.1.1
?? even if IP address is192.168.9.2
If somebody runs calico enabled cluster which was created lately and it works for you, please be kind run commands above and paste results here.
Thank you
The text was updated successfully, but these errors were encountered: