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
Pod been allocated an IP that doesn't belongs to podSubnet in v1.12.1 #70785
Comments
BTW
They are only a little bit different. |
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😄. But I also noticed that, And I'm not sure that is the cause of my issue. If I boot the And I just noticed another unexpected behavior. When I join and mark my
Informationkubeadm alpha commands to add master-02
kubeadm-config-m0.yaml
kubeadm-config-m1.yaml
|
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? |
I had the same problem, i reset the node3 ,when i runinng “kubeadm alpha phase kubelet write-env-file --config kubeadm-master.config ”,dispaly "didn't recognize types with GroupVersionKind: [kubeadm.k8s.io/v1alpha3, Kind=ClusterConfiguration]". |
OK, I've confirm that too. @zhangyan1022wo Thank you so much for spotting that. It seems this is a duplicated issue of kubernetes/kubeadm#1171. Closed. |
What happened:
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
master-02
andmaster-03
own an IP that doesn't belongs to the CIDR I set, but belongs to 172.17.0.0/16 (a.k.a. docker0 CIDR). Here is an example:I'm not sure if i should post this issue to
kubernetes
orcalico
, but I used to test v1.11.0 kubernetes with same calico manifest, and it doesn't run into this issue. So I think I should post it here firstSorry 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):
Prerequisite:
v1.12.1
kubeadm
andkubernetes
installed.Reproduce:
Environment:
kubectl version
): v1.12.1uname -a
): Linux centos-7-x86-64-29-80 4.18.12-1.el7.elrepo.x86_64 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Thu Oct 4 09:36:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux/kind bug
/sig Network
The text was updated successfully, but these errors were encountered: