Closed lukasholzer closed 7 months ago
I have the same problem since today. Came out of nowhere. It also happens when scaling up. If you start /usr/local/bin/k3s manually with the root user, the agent connects successfully to the cluster. The systemd service does not seem to get the right permissions.
Downgrading to previous versions of the module does not solve the issue
Seems to be a problem with selinux. Quick and dirty workaround:
module "kube-hetzner" {
postinstall_exec = ["restorecon -v /usr/local/bin/k3s"]
...
}
I confirm this bug and the workaround. I wonder what has changed...
Had the same bug happen for me, the workaround with the postinstall_exec, did it.
It probably something to do with SELINUX and the OS updates. @mysticaltech
@Silvest89 Indeed, I will correct it tonight, see which SELinux rules are needed.
Thankd for the debug folks, it's fixed in v2.11.4.
Description
When applying the config it fails with the following error that k3s could not be executed.
Kube.tf file
Screenshots
Platform
Mac