📖 doc: add node bootstrap troubleshooting doc #4627
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
/cc @vincepri |
k8s-ci-robot
added
the
size/S
| @@ -1,5 +1,23 @@ | |||
| # Troubleshooting | |||
|
|
|||
| ## Node bootstrap failures | |||
|
|
|||
| Failures during Node bootstrapping can have a lot of different causes. For example, ClusterAPI resources might be | |||
There was a problem hiding this comment.
| Failures during Node bootstrapping can have a lot of different causes. For example, ClusterAPI resources might be | |
| Failures during Node bootstrapping can have a lot of different causes. For example, Cluster API resources might be |
| 1. Kubelet: `journalctl -u kubelet --since "1 day ago"` | ||
| (Note: it might be helpful to increase the Kubelet log level by e.g. setting `--v=8` via | ||
| `systemctl edit --full kubelet && systemctl restart kubelet`) | ||
| 1. If Node bootstrapping consistently fails and the kubeadm logs are not verbose enough, the `kubeadm` verbosity |
There was a problem hiding this comment.
this section assumes cloud-init and kubeadm which does not apply to all bootstrap providers, maybe add something like "when using CABPK" at the top or as a separate header
|
Thanks for this write up! It will super helpful to have something where to redirect users in case of problems. (lgtm pending comments above to be addressed) |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
k8s-ci-robot
added
the
approved
sbueringer
force-pushed
the
pr-add-troubleshooting-doc
branch
from
46efeb2 to
36bae1a
Compare
|
@fabriziopandini @CecileRobertMichon ptal. I added it to the section title. |
k8s-ci-robot
added
the
lgtm
|
/lgtm |
What this PR does / why we need it:
Adds some guidance how node bootstrap failures can be debugged.
xref: #4583 (comment)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes -