Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

kube-proxy cannot set the conntrack hashsize inside a container #240

Open
twelho opened this issue Jun 24, 2020 · 0 comments
Open

kube-proxy cannot set the conntrack hashsize inside a container #240

twelho opened this issue Jun 24, 2020 · 0 comments

Comments

@twelho
Copy link
Contributor

twelho commented Jun 24, 2020

When running make integration-tests-container, kube-proxy in node0 tries to update /sys/module/nf_conntrack/parameters/hashsize in case it is not large enough, but this fails since it can only be updated from the root netns (on host). This causes the integration test to fail, the first node never completes initialization.

This issue seems to only show up with high nproc counts, tested on a system with 24 hardware threads. Updating the hashsize value requires root, so maybe instead of making wksctl directly write it, we could have a preflight check?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant