Skip to content

Support separate inbound and outbound subnet skips - #15496

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

Support separate inbound and outbound subnet skips#15496
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 config.linkerd.io/skip-subnets setting cannot distinguish inbound source-subnet exclusions from outbound destination-subnet exclusions. This makes it impossible to configure the desired behavior for both traffic directions.

Solution

Add config.linkerd.io/skip-inbound-subnets and config.linkerd.io/skip-outbound-subnets pod annotations, chart values, and proxy-init argument wiring. The existing skip-subnets annotation and value remain backwards compatible.

This is the Linkerd control-plane companion to linkerd/linkerd2-proxy-init#792 and addresses #10726.

Validation

  • go test ./pkg/inject -run '^TestGetOverriddenValues$' -count=1
  • go test ./pkg/charts/linkerd2 ./pkg/k8s
  • git diff --check

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

Problem: proxy-init cannot independently exclude inbound source subnets and outbound destination subnets from redirection.

Solution: expose separate subnet settings through pod annotations and chart values while preserving the existing skip-subnets setting.

Validation: go test ./pkg/inject -run '^TestGetOverriddenValues$' -count=1; go test ./pkg/charts/linkerd2 ./pkg/k8s
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