Remove NLB UDP paragraph (#717)

dumlutimuralp · web-flow · commit d33749da5303 · 2025-10-22T11:45:11.000-05:00
AWS NLB supports IPv6 for UDP since October 2024. Hence removed the last paragraph which is obsolete.
diff --git a/latest/bpg/networking/ipv6.adoc b/latest/bpg/networking/ipv6.adoc
@@ -120,6 +120,5 @@ EKS supports IPv6 for Pods running on Fargate. Pods running on Fargate will cons
 
 *The upstream in-tree Kubernetes service controller does not support IPv6*. We recommend using the https://kubernetes-sigs.github.io/aws-load-balancer-controller[most recent version] of the AWS Load Balancer Controller add-on. The LBC will only deploy a dual-stack NLB or a dual-stack ALB upon consuming corresponding kubernetes service/ingress definition annotated with: `"alb.ingress.kubernetes.io/ip-address-type: dualstack"` and `"alb.ingress.kubernetes.io/target-type: ip"`
 
-AWS Network Load Balancer does not support dual-stack UDP protocol address types. If you have strong requirements for low-latency, real-time streaming, online gaming, and IoT, we recommend running IPv4 clusters. To learn more about managing health checks for UDP services, please refer to https://aws.amazon.com/blogs/containers/how-to-route-udp-traffic-into-kubernetes/["`How to route UDP traffic into Kubernetes`"].
 
 

Original file line number	Diff line number	Diff line change
`@@ -120,6 +120,5 @@ EKS supports IPv6 for Pods running on Fargate. Pods running on Fargate will cons`
`120`	`120`
`121`	`121`	The upstream in-tree Kubernetes service controller does not support IPv6. We recommend using the https://kubernetes-sigs.github.io/aws-load-balancer-controller[most recent version] of the AWS Load Balancer Controller add-on. The LBC will only deploy a dual-stack NLB or a dual-stack ALB upon consuming corresponding kubernetes service/ingress definition annotated with: `"alb.ingress.kubernetes.io/ip-address-type: dualstack"` and `"alb.ingress.kubernetes.io/target-type: ip"`
`122`	`122`
`123`		-AWS Network Load Balancer does not support dual-stack UDP protocol address types. If you have strong requirements for low-latency, real-time streaming, online gaming, and IoT, we recommend running IPv4 clusters. To learn more about managing health checks for UDP services, please refer to https://aws.amazon.com/blogs/containers/how-to-route-udp-traffic-into-kubernetes/["`How to route UDP traffic into Kubernetes`"].
`124`	`123`
`125`	`124`