Closed svanharmelen closed 1 week ago
Hi @svanharmelen! Thanks for pointing that out. Indeed, k0s's kube-proxy image is missing all the symlinks to kmod :-( That will be fixed ASAP.
Cool, then we will wait for the fixed version to be released!
We did search for a repo that holds the build files and/or Dockerfile for the kube-proxy container to see if we could create a PR or make a custom build ourselves, but we failed to find such repo.
Did we miss it or is that all stored in a private repo?
Thanks!
Can you check if the latest point releases for 1.29/1.30 fixed the issue for you?
Did we miss it or is that all stored in a private repo?
Indeed, they currently are. It's planned to open them up soonish.
Yup, 1.30.2 seems to work as expected again. Thanks for the help @twz123 👍🏻
Before creating an issue, make sure you've checked the following:
Platform
Version
1.30.1+k0s
Sysinfo
`k0s sysinfo`
What happened?
We tried to update from 1.28.x to the latest 1.30.x but the cluster failed to start after using the new binary (together with the k0s-airgap-bundle-v1.30.1+k0s.0-arm64 bundle). When looking closer at the logs we noticed this in the kube-proxy logs:
Steps to reproduce
k0s controller --enable-worker --no-taints --config k0s.yaml
Expected behavior
A working cluster
Actual behavior
Cluster fails to start (see error output above) and prevents networking to start.
Screenshots and logs
Additional context
No response