From d27e177c88667f801f0cc3e5968609f87659d36d Mon Sep 17 00:00:00 2001 From: Antonio Ojea Date: Wed, 25 Aug 2021 13:33:44 +0200 Subject: [PATCH] Update content/en/docs/concepts/services-networking/dual-stack.md Co-authored-by: Tim Bannister --- .../en/docs/concepts/services-networking/dual-stack.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/services-networking/dual-stack.md b/content/en/docs/concepts/services-networking/dual-stack.md index a7ee5360a6..21ecd20a7a 100644 --- a/content/en/docs/concepts/services-networking/dual-stack.md +++ b/content/en/docs/concepts/services-networking/dual-stack.md @@ -60,9 +60,13 @@ To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments: * kube-proxy: * `--cluster-cidr=,` * kubelet: - * when there is no `--cloud-provider` the administrator can pass a comma-separated pair of IPs via `--node-ip` - to manually configure dual-stack `node.status.addresses`. HostNetwork pods will report these IPs in `.status.podIPs`. - All `podIPs` in a node will match the IP family preference defined by the `node.status.addresses` on that node. + * when there is no `--cloud-provider` the administrator can pass a comma-separated pair + of IP addresses via `--node-ip` to manually configure dual-stack `.status.addresses` + for that Node. + If a Pod runs on that node in HostNetwork mode, the Pod reports these IP addresses in its + `.status.podIPs` field. + All `podIPs` in a node match the IP family preference defined by the + `.status.addresses` field for that Node. {{< note >}} An example of an IPv4 CIDR: `10.244.0.0/16` (though you would supply your own address range)