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

don't set conntrack parameters in kube-proxy #2241

Merged
merged 1 commit into from
May 12, 2021
Merged

don't set conntrack parameters in kube-proxy #2241

merged 1 commit into from
May 12, 2021

Commits on May 12, 2021

  1. don't set conntrack parameters in kube-proxy 

    It seems the kernel doesn't allow to set some conntrack fields
from non-init netns because they are global, so setting it in a
namespaces leaks it to other namespace:

netfilter: conntrack: Make global sysctls readonly in non-init netns
torvalds/linux@671c54e

By default kube-proxy tries to set nf_conntrack_max, that is readonly,
hence failing and the kproxy pods fail to start crashlooping.
    @aojea
    Antonio Ojea authored and aojea committed May 12, 2021
    Configuration menu
    Copy the full SHA
    a66e833 View commit details
    Browse the repository at this point in the history