-
Notifications
You must be signed in to change notification settings - Fork 275
Open
Description
Hi there,
We are currently attempting to use IPv6 NAT policies to support the Kubernetes containerPort mapping feature (specifically for environments where dual-stack or IPv6-only ingress traffic is required).
While the IPv4 NAT policy works as expected—correctly translating and routing traffic to the pod—the IPv6 NAT policy does not appear to take effect or handle the translation correctly under similar configurations.
Could someone take a look at this? We are currently blocked by this inconsistency in dual-stack and IPv6-only support. Any guidance or suggested workarounds would be much appreciated.

Metadata
Metadata
Assignees
Labels
No labels