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 kubeadm troubleshooting guide #9028

Merged
merged 1 commit into from Jun 12, 2018

Conversation

Projects
None yet
6 participants
@detiber
Copy link
Member

detiber commented Jun 11, 2018

Updates to the kubeadm troubleshooting guide

@k8sio-netlify-preview-bot

This comment has been minimized.

Copy link
Collaborator

k8sio-netlify-preview-bot commented Jun 11, 2018

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

Built with commit 476fb3d

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

@k8sio-netlify-preview-bot

This comment has been minimized.

Copy link
Collaborator

k8sio-netlify-preview-bot commented Jun 11, 2018

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

Built with commit f7f56ca

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

@Bradamant3

This comment has been minimized.

Copy link
Member

Bradamant3 commented Jun 11, 2018

/assign

@neolit123
Copy link
Member

neolit123 left a comment

ran the MD through a word processor.

we didn't discuss the names for those new labels to filter k/kubeadm filter issues, by known-bugs/has-solution etc. i think it was agreed to add them in this guide, but i guess this can wait post the doc freeze.

Then restart `kubelet`:
#### Services with externalTrafficPolicy=Local are not reachable
On nodes where the hostname for the kubelet is overriden uisng the `--hostname-override` option, kube-proxy will default to treating 127.0.0.1 as the node IP, which results in rejecting connections for Services configured for `externalTrafficPolicy=Local`. This situation can be verified by checking the output of `kubectl -n kube-system logs <kube-proxy pod name>`:

This comment has been minimized.

@neolit123

neolit123 Jun 11, 2018

Member

overriden uisng -> overridden using

`Vagrantfile`[ubuntu-vagrantfile](https://github.com/errordeveloper/k8s-playground/blob/22dd39dfc06111235620e6c4404a96ae146f26fd/Vagrantfile#L11) for how this can be achieved.
- If you are using VirtualBox (directly or via Vagrant), you will need to
ensure that `hostname -i` returns a routable IP address. By default the first
interface is connected to a non-routeable host-only network. A work around

This comment has been minimized.

@neolit123

neolit123 Jun 11, 2018

Member

non-routeable -> non-routable ?

@@ -52,7 +52,7 @@ This may be caused by a number of problems. The most common are:
Check the system log file (e.g. `/var/log/message`) or examine the output from `journalctl -u kubelet`. If you see something like the following:

```shell
error: failed to run Kubelet: failed to create kubelet:
error: failed to run Kubelet: failed to create kubelet:
misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs"

This comment has been minimized.

@neolit123

neolit123 Jun 11, 2018

Member

from docker -> from the Docker

This comment has been minimized.

@detiber

detiber Jun 11, 2018

Author Member

This is the error output from the kubelet when the cgroup driver does not match.

This comment has been minimized.

@neolit123

neolit123 Jun 11, 2018

Member

oh...(right, nvm then).

```

Then you may be missing `ebtables`, `ethtool` or a similar executable on your Linux machine. You can install them with the following commands:
Then you may be missing `ebtables`, `ethtool` or a similar executable on your node. You can install them with the following commands:

- For ubuntu/debian users, run `apt install ebtables ethtool`.

This comment has been minimized.

@neolit123

neolit123 Jun 11, 2018

Member

ubuntu/debian -> Ubuntu/Debian.

@timothysc

This comment has been minimized.

Copy link
Member

timothysc commented Jun 11, 2018

/hold

We need to update the examples around changes from v1alpha1 to v1alpha2, this will likely be a bulk of inbound issues.

@detiber detiber force-pushed the detiber:updateTroubleshootingGuide branch from 476fb3d to f7f56ca Jun 11, 2018

@timothysc

This comment has been minimized.

Copy link
Member

timothysc commented Jun 11, 2018

@detiber we can proceed with this and follow up, or add the content now, your choice.

@detiber

This comment has been minimized.

Copy link
Member Author

detiber commented Jun 12, 2018

@timothysc lets proceed with this for now and we can follow up later. I think the upgrade issues are more pressing atm.

@timothysc
Copy link
Member

timothysc left a comment

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm label Jun 12, 2018

@Bradamant3

This comment has been minimized.

Copy link
Member

Bradamant3 commented Jun 12, 2018

/approve

@k8s-ci-robot

This comment has been minimized.

Copy link

k8s-ci-robot commented Jun 12, 2018

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bradamant3, timothysc

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

@k8s-ci-robot k8s-ci-robot merged commit 3728493 into kubernetes:master Jun 12, 2018

3 of 4 checks passed

tide Not mergeable.
Details
cla/linuxfoundation detiber authorized
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
deploy/netlify Deploy preview ready!
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.