Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: kubernetes/website
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cb5c5e3c67366e8a4cd8ed361a3f7c08ff8e564c
Choose a base ref
..
head repository: kubernetes/website
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: ba282349285bca35661b1da78761621df268cbe0
Choose a head ref
Showing with 4 additions and 3 deletions.
  1. +4 −3 content/en/docs/concepts/services-networking/dual-stack.md
7 changes: 4 additions & 3 deletions content/en/docs/concepts/services-networking/dual-stack.md
Original file line number Diff line number Diff line change
@@ -66,9 +66,10 @@ To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments:
* `--cluster-cidr=<IPv4 CIDR>,<IPv6 CIDR>`
* kubelet:
* `--node-ip=<IPv4 IP>,<IPv6 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
explicit `--node-ip` if you want to override the node IPs chosen by the cloud provider.
* This option is required for bare metal dual-stack nodes (nodes that do not define a
cloud provider with the `--cloud-provider` flag). If you are using a cloud provider
and choose to override the node IPs chosen by the cloud provider, set the
`--node-ip` option.
* (The legacy built-in cloud providers do not support dual-stack `--node-ip`.)

{{< note >}}