From 4001b9cd7a217076b64aba6c07374914f3ae6496 Mon Sep 17 00:00:00 2001 From: Antonio Ojea Date: Wed, 25 Aug 2021 12:29:12 +0200 Subject: [PATCH] Update dual-stack node.status Add missing comment about node addresses and podIPs order: https://github.com/kubernetes/kubernetes/pull/95239 https://github.com/kubernetes/kubernetes/pull/97979 --- content/en/docs/concepts/services-networking/dual-stack.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/concepts/services-networking/dual-stack.md b/content/en/docs/concepts/services-networking/dual-stack.md index a85226beed..a7ee5360a6 100644 --- a/content/en/docs/concepts/services-networking/dual-stack.md +++ b/content/en/docs/concepts/services-networking/dual-stack.md @@ -59,6 +59,10 @@ To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments: * `--node-cidr-mask-size-ipv4|--node-cidr-mask-size-ipv6` defaults to /24 for IPv4 and /64 for IPv6 * 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. {{< note >}} An example of an IPv4 CIDR: `10.244.0.0/16` (though you would supply your own address range)