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

Update create-cluster-kubeadm.md #10560

Closed
wants to merge 1 commit into from
Closed

Conversation

lanoxx
Copy link

@lanoxx lanoxx commented Oct 9, 2018

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

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
@kubernetes-docs-i18n-bot kubernetes-docs-i18n-bot added the language/en Issues or PRs related to English language label Oct 9, 2018
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 9, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: jaredbhatti

If they are not already assigned, you can assign the PR to them by writing /assign @jaredbhatti in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8sio-netlify-preview-bot
Copy link
Collaborator

Deploy preview for kubernetes-io-master-staging ready!

Built with commit b66153b

https://deploy-preview-10560--kubernetes-io-master-staging.netlify.com

@neolit123
Copy link
Member

@lanoxx
please sign the CLI if you want to contribute!

sorry but this is not correct:

It is necessary to join a node to the master otherwise the CoreDNS pods will be unable to start.

you can have a single-node cluster with the coredns pods running perfectly fine, so the issue here is something else.

I am using Kubernetes 1.12 and I am running into this isssue. I have setup Flannel using the kubectl apply syntax from the documentation but coredns pods are not starting up

there is a known bug in flannel with 1.12. try this command:
flannel-io/flannel#1045 (comment)

or you can try the weavenet plugin instead.

if you find bugs please report them in the kubernetes/kubeadm issue tracker.
thanks.

/close

@k8s-ci-robot
Copy link
Contributor

@neolit123: Closing this PR.

In response to this:

@lanoxx
please sign the CLI if you want to contribute!

sorry but this is not correct:

It is necessary to join a node to the master otherwise the CoreDNS pods will be unable to start.

you can have a single-node cluster with the coredns pods running perfectly fine, so the issue here is something else.

I am using Kubernetes 1.12 and I am running into this isssue. I have setup Flannel using the kubectl apply syntax from the documentation but coredns pods are not starting up

there is a known bug in flannel with 1.12. try this command:
flannel-io/flannel#1045 (comment)

or you can try the weavenet plugin instead.

if you find bugs please report them in the kubernetes/kubeadm issue tracker.
thanks.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. language/en Issues or PRs related to English language size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants