Skip to content
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

enabling CNI is broken coreDNS doesnt come up. #7466

Closed
medyagh opened this issue Apr 7, 2020 · 1 comment
Closed

enabling CNI is broken coreDNS doesnt come up. #7466

medyagh opened this issue Apr 7, 2020 · 1 comment

Comments

@medyagh
Copy link
Member

medyagh commented Apr 7, 2020

CNI is broken on head:

after adding ew wait component in this PR #7460
it was revealed that after we start mnikube with these CNI/ args

--network-plugin=cni 
--extra-config=kubelet.network-plugin=cni
--extra-config=kubeadm.pod-network-cidr=192.168.111.111/16 

the coreDNS never comes up becuase it says network is not ready.

https://storage.googleapis.com/minikube-builds/logs/7460/b880469/KVM_Linux.html#fail_TestStartStop%2fgroup%2fnewest-cni

I replicated this on hyperkit:


./out minikube start -p newest-cni-20200406T232337.63805791-16483 --memory=2200 --alsologtostderr -v=3 --wait=true --feature-gates ServerSideApply=true --network-plugin=cni --extra-config=kubelet.network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.111.111/16 --driver=hyperkit  --kubernetes-version=v1.18.0

the kubectl describe node says: node netwrok is not ready.



@medyagh medyagh changed the title newest-cni core-dns pending TestStartStop/group/newest-cni fails on waiting for coreDNS Apr 7, 2020
@medyagh medyagh changed the title TestStartStop/group/newest-cni fails on waiting for coreDNS enabling CNI is broken coreDNS doesnt come up. Apr 7, 2020
@tstromberg
Copy link
Contributor

Dupe of #7354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants