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

update for KUBE-IPTABLES-HINT (and other 2022-ness) #3

Merged
merged 3 commits into from
Apr 12, 2022

Commits on Mar 31, 2022

  1. Drop support for iptables 1.8.3, update distro version notes

    iptables 1.8.3 has a bug that makes it hang forever in certain cases,
    requiring us to use "timeout" in the script. However, 1.8.4 is over
    two years old at this point, and even Debian buster-backports has
    1.8.5, so there's no reason to keep supporting 1.8.3. So remove that.
    
    Also update the README and test Dockerfiles to use newer versions of
    Fedora and Alpine to get a new-enough version.
    danwinship committed Mar 31, 2022
    Configuration menu
    Copy the full SHA
    e56c74e View commit details
    Browse the repository at this point in the history
  2. Default to nft over legacy in ambiguous situations

    Systems these days are more likely to be using iptables-nft than
    iptables-legacy, so if there are no rules in either table, guess "nft"
    rather than "legacy".
    danwinship committed Mar 31, 2022
    Configuration menu
    Copy the full SHA
    2a9e1a1 View commit details
    Browse the repository at this point in the history
  3. Try to resolve nft/legacy based on KUBE-IPTABLES-HINT / KUBE-KUBELET-…

    …CANARY first
    
    Check for the (1.24+) KUBE-IPTABLES-HINT or (1.17+)
    KUBE-KUBELET-CANARY chain first, and only fall back to counting total
    number of legacy vs nft rules if we don't find that.
    danwinship committed Mar 31, 2022
    Configuration menu
    Copy the full SHA
    70d7897 View commit details
    Browse the repository at this point in the history