NAT46/64 follow-ups #19264

New issue

Copy link

New issue

Copy link

Open

Open

NAT46/64 follow-ups#19264

Copy link

Assignees

Labels

area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/loadbalancingImpacts load-balancing and Kubernetes service implementationsImpacts load-balancing and Kubernetes service implementationskind/featureThis introduces new functionality.This introduces new functionality.

Description

borkmann

opened on Mar 30, 2022

Issue body actions

• pmtu discovery for 4->6 (tc & XDP). for 6->4 not needed.
• double check if we need bpftool update wrt probing
• k8s svc integration w/ pods
  • documentation once complete
• store NAT pol in svc handler's state (link)
• We should be able to derive the NAT pol from svc.svcNatPolicy (link)
• error handling for backend deletion (link)
• unit test for none <=> nat46 <=> nat64 (link)
• migrate low-level map additions to lbmap only? (link)
• deletion of exact backends (link)
• sync errors for controller bpf-map-sync-cilium_lb6_backends_v2 (reported by Jarno)

Metadata

Metadata

Assignees

• 
  borkmann

Labels

area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/loadbalancingImpacts load-balancing and Kubernetes service implementationsImpacts load-balancing and Kubernetes service implementationskind/featureThis introduces new functionality.This introduces new functionality.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions