Skip to content

Commit d27e177

Browse files
Antonio OjeaTim Bannister
andauthored
Update content/en/docs/concepts/services-networking/dual-stack.md
Co-authored-by: Tim Bannister <[email protected]>
1 parent 4001b9c commit d27e177

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

content/en/docs/concepts/services-networking/dual-stack.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -60,9 +60,13 @@ To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments:
6060
* kube-proxy:
6161
* `--cluster-cidr=<IPv4 CIDR>,<IPv6 CIDR>`
6262
* kubelet:
63-
* when there is no `--cloud-provider` the administrator can pass a comma-separated pair of IPs via `--node-ip`
64-
to manually configure dual-stack `node.status.addresses`. HostNetwork pods will report these IPs in `.status.podIPs`.
65-
All `podIPs` in a node will match the IP family preference defined by the `node.status.addresses` on that node.
63+
* when there is no `--cloud-provider` the administrator can pass a comma-separated pair
64+
of IP addresses via `--node-ip` to manually configure dual-stack `.status.addresses`
65+
for that Node.
66+
If a Pod runs on that node in HostNetwork mode, the Pod reports these IP addresses in its
67+
`.status.podIPs` field.
68+
All `podIPs` in a node match the IP family preference defined by the
69+
`.status.addresses` field for that Node.
6670

6771
{{< note >}}
6872
An example of an IPv4 CIDR: `10.244.0.0/16` (though you would supply your own address range)

0 commit comments

Comments
 (0)