Skip to content

ipv6 portmapping policy dose not work #2590

@ruicao93

Description

@ruicao93

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.

image image image image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions