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.

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

Make iptables initialization error non fatal #1497

Merged
merged 1 commit into from
Nov 9, 2020

Commits on Nov 9, 2020

  1. Make iptables initialization error non fatal

    In large scale clusters, xtables lock may be hold by kubelet/
    kube-proxy/ portmap for a long time, especially when there are many
    service rules in nat table. antrea-agent may not be able to acquire the
    lock in short time. If the agent blocks on the lock or quit itself, the
    CNI server won't be running, causing all CNI requests to fail.  If the
    Pods' restart policy is Always and there are dead Pods, container
    runtime will keep retrying calling CNIs, during which portmap is called
    first, leading to more xtables lock contention.
    
    This patch makes iptables initialization error non fatal and uses a
    goroutine to retry it until success. The agent will start the CNI server
    anyway and handle the CNI Del requests but won't handle CNI Add requests
    until the network is ready.
    tnqn committed Nov 9, 2020
    Configuration menu
    Copy the full SHA
    ed2318e View commit details
    Browse the repository at this point in the history