Skip to content

Support separate inbound and outbound subnet skips#792

Draft
hooiv wants to merge 1 commit into
linkerd:mainfrom
hooiv:feat/separate-subnet-skips
Draft

Support separate inbound and outbound subnet skips#792
hooiv wants to merge 1 commit into
linkerd:mainfrom
hooiv:feat/separate-subnet-skips

Conversation

@hooiv

@hooiv hooiv commented Jul 20, 2026

Copy link
Copy Markdown

Problem

The existing --subnets-to-ignore option only adds source-subnet RETURN rules to the inbound chain. Outbound traffic to the same subnets is still redirected through the proxy.

Solution

Add --inbound-subnets-to-ignore and --outbound-subnets-to-ignore. The legacy option remains supported as an inbound-only setting. Outbound exclusions match destination addresses.

This is the proxy-init implementation for linkerd/linkerd2#10726; the injector and chart wiring are submitted separately.

Validation

  • go test ./pkg/iptables ./proxy-init/cmd
  • git diff --check

Signed-off-by: ADITYA CHAUHAN hooiv@users.noreply.github.com

Problem: skip-subnets only excludes inbound traffic, so outbound packets destined for those subnets are still redirected through the proxy.

Solution: add explicit inbound and outbound subnet options while preserving skip-subnets as the backwards-compatible inbound setting.

Validation: go test ./pkg/iptables ./proxy-init/cmd
Signed-off-by: hooiv <125276621+hooiv@users.noreply.github>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant