From 5056816f28830beee2114ba7f0c347d6349cb8f7 Mon Sep 17 00:00:00 2001 From: Antonio Ojea Date: Tue, 4 Apr 2023 15:44:30 +0200 Subject: [PATCH] Update content/en/docs/reference/networking/virtual-ips.md Co-authored-by: Tim Bannister --- content/en/docs/reference/networking/virtual-ips.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md index 6c2cdaacf7460..e6a6ef135c077 100644 --- a/content/en/docs/reference/networking/virtual-ips.md +++ b/content/en/docs/reference/networking/virtual-ips.md @@ -314,8 +314,9 @@ for the `service-cluster-ip-range`, there is no limitations for IPv4 and for IPv users can use masks equal or larger than /64 (previously it was /108). Users now will be able to inspect the IP addresses assigned to their Services, and -new network APIs, like Gateway API, can use this new object to extend the Kubernetes -networking capabilities overcoming the limitations of current Services API. +Kubernetes extensions such as the [Gateway](https://gateway-api.sigs.k8s.io/) API, can use this new +IPAddress object kind to enhance the Kubernetes networking capabilities, going beyond the limitations of +the built-in Service API. ```shell kubectl get services