-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Update create-cluster-kubeadm.md #10560
Conversation
Clarify in the documentation that a node must be joined before CoreDNS can start. I was mislead by the documentation into believing that the CoreDNS pods need to be running before I can join a node. See also this discussion on Stackoverflow: https://stackoverflow.com/questions/52609257/coredns-in-pending-state-in-kubernetus-cluster
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Deploy preview for kubernetes-io-master-staging ready! Built with commit b66153b https://deploy-preview-10560--kubernetes-io-master-staging.netlify.com |
@lanoxx sorry but this is not correct:
you can have a single-node cluster with the coredns pods running perfectly fine, so the issue here is something else.
there is a known bug in flannel with 1.12. try this command: or you can try the weavenet plugin instead. if you find bugs please report them in the /close |
@neolit123: Closing this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Clarify in the documentation that a node must be joined before CoreDNS can start. I was mislead by the documentation into believing that the CoreDNS pods need to be running before I can join a node.
See also this discussion on Stackoverflow:
https://stackoverflow.com/questions/52609257/coredns-in-pending-state-in-kubernetus-cluster