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

Ability to configure wait for the xtables lock #58

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

Commits on Oct 4, 2023

  1. Ability to configure wait for the xtables lock

    Any invocation of the iptables command results in an xtables lock, which
    can lead to the iptables command exiting(4).  Racy systems which make
    use of inspecting iptables can cause an error.
    
    However, maybe this is ultimately not an issue as kubernetes will retry
    failed pods.
    
    > IPTABLES(8):
      -w, --wait [seconds]
              Wait for the xtables lock.  To prevent multiple instances of the
              program from running concurrently, an attempt will be made to obtain
              an exclusive lock at launch.  By default, the program will exit if
              the lock cannot be obtained.  This option will make the program wait
              (indefinitely or for optional seconds) until the exclusive lock can
              be obtained.
    
    Signed-off-by: נυαη נυαηѕση <john@dewey.ws>
    retr0h committed Oct 4, 2023
    Configuration menu
    Copy the full SHA
    d246770 View commit details
    Browse the repository at this point in the history