Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Pod been allocated an IP that doesn't belongs to podSubnet in v1.12.1 #70785
Hi, I have three nodes, they are well prepared for deploying kubernetes and they have password-less login ssh to each other.
I'm trying to deploy a kubernetes v1.12.1 HA master cluster with my script on them. I set my CIDR to 10.244.0.0/16. But after the script finished it's job, i found all pods on
I'm not sure if i should post this issue to
Sorry for I don't know how it happened clearly yet. I'm not sure if this is caused by my misconfigured or a bug, I've tried read controller log, calico log, but I failed to catch any clue. Is there any more information I may provide? Or any clue I can followed to continuing my debug? Thanks.
What you expected to happen:
Pods own an IP belongs to the podSubnet I set.
How to reproduce it (as minimally and precisely as possible):
They are only a little bit different.
referenced this issue
Nov 8, 2018
I've noticed that your calico node isn't fully healthy: Only 1 container among 2 is running. Most likely it's install-cni.
Thanks for reminding
And I just noticed another unexpected behavior. When I join and mark my
kubeadm alpha commands to add master-02
I just rebuild my cluster with calico 3.1.3, and all containers are healthy now. My podSubnet is still
@anfernee Hi, sorry for bothering. Any chance to provide me some feed back? Thanks. These days I also tried to create my cluster manually following the official guide Creating Highly Available Clusters with kubeadm. And I got a broken cluster almost same as the one I created with my script: Right after I run
The only difference between this guide and my script is:
So I'm really confused. Am I the only one who meet this?