ipv6 portmapping policy dose not work
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 694
- Forks
- 304
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 28
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IPv4 and IPv6 NAT policy configurations shown in the attached screenshots and reproduce the Kubernetes containerPort mapping behavior in a dual-stack or IPv6-only environment. Compare whether IPv6 traffic is translated and routed as the IPv4 traffic is; done means the IPv6 NAT policy takes effect consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100