From 4e5013df3a363450e78e79e9d1726bba14b6f1ee Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Tue, 5 Sep 2023 14:01:32 -0400 Subject: [PATCH] Update content/en/docs/concepts/services-networking/dual-stack.md Co-authored-by: Tim Bannister --- content/en/docs/concepts/services-networking/dual-stack.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/dual-stack.md b/content/en/docs/concepts/services-networking/dual-stack.md index 84f87f386c3e0..ac2d1ecfde2ae 100644 --- a/content/en/docs/concepts/services-networking/dual-stack.md +++ b/content/en/docs/concepts/services-networking/dual-stack.md @@ -66,8 +66,10 @@ To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments: * `--cluster-cidr=,` * kubelet: * `--node-ip=,` - * This is required for "bare metal" dual-stack nodes (i.e., nodes with no - `--cloud-provider`). If you are using a cloud provider, you only need to pass an + * this is required for dual-stack nodes in "bare metal" mode (nodes where you do not specify + `--cloud-provider` as a command line argument to the kubelet). The kubelet publishes the + IP addresses that you specify, as `.status.addresses`. + If you are using a cloud provider integration, you only need to pass an explicit `--node-ip` if you want to override the node IPs chosen by the cloud provider. * (The legacy built-in cloud providers do not support dual-stack `--node-ip`.)