Skip to content
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

Document iptables version mismatch pitfall #4406

Merged
merged 1 commit into from
May 10, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,15 @@ With this config you can start your controller as usual. Any workers will need t
k0s worker --profile coreos [TOKEN]
```

## iptables veresion mismatch

If the running kernel has firewall rules created using an iptables version
newer than the version shipped with k0s, the Kubernetes network will [not
work](https://www.mirantis.com/blog/networking-problems-after-installing-kubernetes-1-25-or-after-upgrading-your-host-os-this-might-be-your-problem).

To solve this, make sure that the iptables version used on host is same version
as bundled with k0s. The k0s version is found in `/var/lib/k0s/bin`.

## Profiling

We drop any debug related information and symbols from the compiled binary by utilzing `-w -s` linker flags.
Expand Down
Loading