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.

Sign up for GitHub

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

Jump to bottom

fix: ensure nf_conntrack module loaded for kube-proxy. #743

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: ensure nf_conntrack module loaded for kube-proxy. #743

wants to merge 1 commit into from

Commits on Oct 18, 2024

  1. fix: ensure nf_conntrack module loaded for kube-proxy. 

    This patch ensures that the `nf_conntrack` kernel module is loaded
before the `kube-proxy` service is started so it can read some
necessary conntrack module-related params from procfs.

Previously, although the `kube-proxy` service 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:
* Cilium [automatically loads `iptable_nat`](https://github.com/cilium/cilium/blob/63cd391f93b4e2c865268241d384504348672042/pkg/datapath/iptables/iptables.go#L367-L368)
after a small startup delay, whose dependency tree includes `nf_conntrack`
* starting firewalld/ufw/most other firewall services
* setting iptables/nftables rules which imply session tracking

By explicitly loading `nf_conntrack` from the `kube-proxy` service
wrapper directly, it should ensure the procfs values kube-proxy reads
are always present on startup.

Signed-off-by: Nashwan Azhari <[email protected]>
    @aznashwan
    aznashwan committed Oct 18, 2024
    Configuration menu
    Copy the full SHA
    dc3e6d5 View commit details
    Browse the repository at this point in the history