Update on 10-bootstrapping-kubernetes-workers.md and 11-tls-bootstrapping-kubernetes-workers.md #352
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
added additional flag --fail-swap-on to kubelet.service for both worker nodes
After starting kubelet and kubelet-proxy, it would show "no resource found" when checking in the controlplane.
checking back on the worker node
systemctl status kubelet
shows that the process is stuck looping in restarting mode. Kubelet apparently could not be run on swap memory (which I think is provisioned by default on all vagrant boxes) hence the addition of the flag.