[Backport 1.30] fix: ensure nf_conntrack module loaded for kubelite. #4728
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch ensures that the
nf_conntrack
kernel module is loaded beforekubelite
is started as the ProxyServer needs to read some conntrack module-related params from procfs.Previously, although the it would always crashed if the module wasn't loaded, this wasn't that common of an occurrence in practice as there are quite a few ways
nf_conntrack
gets loaded transparently:iptable_nat
after a small startup delay, whose dependency tree includesnf_conntrack
By explicitly loading
nf_conntrack
before startingkubelite
, it should ensure the procfs values ther ProxyServer reads are always present on startup.Summary
Changes
Testing
Possible Regressions
Checklist
Notes