hetzner-kube: adding workers fails on Wireguard configuration

When adding a worker the install process stops at Wireguard configuration.

command:systemctl enable wg-quick@wg0 && systemctl restart wg-quick@wg0 && systemctl enable overlay-route.service && systemctl restart overlay-route.service stdout:Created symlink /etc/systemd/system/multi-user.target.wants/wg-quick@wg0.service → /lib/systemd/system/wg-quick@.service. Job for wg-quick@wg0.service failed because the control process exited with error code. See "systemctl status wg-quick@wg0.service" and "journalctl -xe" for details.

This seems to be related to: https://github.com/adrianmihalko/raspberrypiwireguard/issues/11

About this issue

Original URL
State: open
Created 4 years ago
Comments: 17 (5 by maintainers)

Commits related to this issue

fix ubuntu hwe-18.04 kernel patch Incorporated the cloud-config from https://github.com/xetys/hetzner-kube/issues/329#issuecomment-651561356 — committed to stevek-pro/hetzner-kube by stevek-pro 4 years ago

Most upvoted comments

Looks like wireguard is borked in the 18.04 distro. Here’s a cloud-init script that should bootstrap your cluster successfully.

my-k8s-cluster-cloud-init

#cloud-config

package_update: true

runcmd:
 - add-apt-repository ppa:wireguard/wireguard
 - apt-get update
 - apt-get install -y --install-recommends linux-generic-hwe-18.04
 - apt-get install -y wireguard wireguard-dkms wireguard-tools
 - modprobe wireguard
 - lsmod | grep wireguard

Can be invoked via;

hetzner-kube cluster create --name my-k8s-cluster --ssh-key my-ssh-key --cloud-init ./my-k8s-cluster-cloud-init

krzko on Jun 30, 2020