You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.
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?
When running
make integration-tests-container
, kube-proxy innode0
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 thehashsize
value requires root, so maybe instead of makingwksctl
directly write it, we could have a preflight check?The text was updated successfully, but these errors were encountered: