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

fix(kuma-dp): fix conntrack collisions #3459

Merged
merged 5 commits into from
Jan 20, 2022

Commits on Dec 9, 2021

  1. fix(kuma-dp): fix conntrack collisions

    Vendors this fix (istio/istio#33572) from Istio
    
    Signed-off-by: John Harris <john.harris@konghq.com>
    johnharris85 committed Dec 9, 2021
    Configuration menu
    Copy the full SHA
    569c12d View commit details
    Browse the repository at this point in the history

Commits on Dec 16, 2021

  1. Configuration menu
    Copy the full SHA
    9a8456a View commit details
    Browse the repository at this point in the history

Commits on Jan 14, 2022

  1. Configuration menu
    Copy the full SHA
    8770c29 View commit details
    Browse the repository at this point in the history

Commits on Jan 19, 2022

  1. Configuration menu
    Copy the full SHA
    27ca5be View commit details
    Browse the repository at this point in the history
  2. chore(*): adjust changes to kuma environment

    As our e2e tests for universal are done from inside of a docker
    container, to make the networking work, we are bridging docker
    network to the host, which results in additional iptables rules
    inside every container within this network. Problem with these
    rules is that it's doing some NAT'ing for DNS udp datagrams with
    addition of randomly picked (during the container startup) port.
    It's problematic for this conntrack change as it works inside
    the `raw` table and among others `PREROUTING` chain and expects
    the datagrams from known port (53), which the earlier described
    NAT'ing is changing. This probably could be fixed by rethinking
    some of the rules, but as it's an edge case, after consultation
    with the team I decided it's not worth the time needed to properly
    solve it and instead I introduced to a `--skip-dns-conntrack-zone-split`
    flag for `kumactl install transparent-proxy`, which allows us to
    skip attaching the conntrack-collision iptables rules. This change
    was necessary for making some of the tests to work (univeral).
    
    I also fixed the code to include our flag for capturing all dns
    traffic and instead of hardcoding port `15053`, to use the one
    from the configuration.
    
    Signed-off-by: Bart Smykla <bartek@smykla.com>
    bartsmykla committed Jan 19, 2022
    Configuration menu
    Copy the full SHA
    b78edcd View commit details
    Browse the repository at this point in the history