-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
Issues when installing and how I solved them #74
Comments
@PieterScheffers Thank you Pieter! I was having an issue with a node marked as I reinstalled the headers and now everything is back to normal 🥳 |
@PieterScheffers did you use the provisioning repository or did you encounter these problems during a manual setup? |
@pstadler I did a manual setup, so it could very well be that I did something wrong. |
I want to mention that
Thank you, Pieter! |
First I must say thank you for this great guide! It gives a very good explanation how to install everything and how it fits together. When installing this I came across some issues. So here I want to contribute back and share the fixes I found that made it work for me.
After a reboot wireguard would not be started. (
wg show
would give an empty result).This can be solved by reinstalling the linux-headers (
apt-get install -y linux-headers-$(uname -r)
) and rebooting. I had this issue coming back multiple times, so I put the install in a oneshot systemd service and putAfter=install-linux-headers
in the[email protected]
files.After
kubeadm init
I would initialize the weave network. But when joining the slaves withkubeadm join
, the slave nodes would stay in the 'not ready' state. When investigating I found it couldn't start the pod network. This could be solved by adding to the masterconfiguration for kubeadm:and the CIDR you want to use can also be passed to weave with:
There would already be a route for the
10.32.0.0/12
(weave) network. So I couldn't setup the extra ip route. (ip route
)As last step I installed the UFW firewall. The cluster would work without it, but after activating the firewall it wouldn't work anymore. The error was because kubelet was being contacted via the Scaleway private IP. To make kubelet be connected to via the Wireguard network I had to add
--node-ip=10.0.1.1
to the/var/lib/kubelet/kubeadm-flags.env
file. (The kubelet systemd file reads the kubelet arguments from that file)The text was updated successfully, but these errors were encountered: