Change:
page is plenty of wrong references to the non defined ` instead.
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/kind bug
/assign
Thanks for solving this so so quick (you are the best ;-)

Discussion:
using the first configured service cluster IP range. * `PreferDualStack`: Allocates both IPv4 and IPv6 cluster IPs for the Service when dual-stack is enabled. If dual-stack is not enabled or supported, it falls back to single-stack behavior. * `RequireDualStack`: Allocates Service `.spec.clusterIPs` from both IPv4 and IPv6 address ranges when dual-stack is enabled. If dual-stack is not enabled or supported, the Service API object creation fails. <del> * Selects the `.spec.ClusterIP` from the list of `.spec.ClusterIPs` based on the address family </del> <ins> * Selects the `.spec.clusterIP` from the list of `.spec.clusterIPs` based on the address family </ins> of the first element in the `.spec.ipFamilies` array. If you would like to define which IP family to use for single stack or define the order of IP

- `["IPv4","IPv6"]` (dual stack) - `["IPv6","IPv4"]` (dual stack) <del> The first family you list is used for the legacy `.spec.ClusterIP` field. </del> <ins> The first family you list is used for the legacy `.spec.clusterIP` field. </ins> ### Dual-stack Service configuration scenarios

1. This Service specification explicitly defines `PreferDualStack` in `.spec.ipFamilyPolicy`. When you create this Service on a dual-stack cluster, Kubernetes assigns both IPv4 and IPv6 addresses for the service. The control plane updates the `.spec` for the Service to record the IP <del> address assignments. The field `.spec.ClusterIPs` is the primary field, and contains both assigned IP addresses; `.spec.ClusterIP` is a secondary field with its value calculated from `.spec.ClusterIPs`. </del> <ins> address assignments. The field `.spec.clusterIPs` is the primary field, and contains both assigned IP addresses; `.spec.clusterIP` is a secondary field with its value calculated from `.spec.clusterIPs`. </ins> <del> * For the `.spec.ClusterIP` field, the control plane records the IP address that is from the </del> <ins> * For the `.spec.clusterIP` field, the control plane records the IP address that is from the </ins> same address family as the first service cluster IP range. <del> * On a single-stack cluster, the `.spec.ClusterIPs` and `.spec.ClusterIP` fields both only list </del> <ins> * On a single-stack cluster, the `.spec.clusterIPs` and `.spec.clusterIP` fields both only list </ins> one address. * On a cluster with dual-stack enabled, specifying `RequireDualStack` in `.spec.ipFamilyPolicy` behaves the same as `PreferDualStack`.

1. This Service specification explicitly defines `IPv6` and `IPv4` in `.spec.ipFamilies` as well as defining `PreferDualStack` in `.spec.ipFamilyPolicy`. When Kubernetes assigns an IPv6 and <del> IPv4 address in `.spec.ClusterIPs`, `.spec.ClusterIP` is set to the IPv6 address because that is the first element in the `.spec.ClusterIPs` array, overriding the default. </del> <ins> IPv4 address in `.spec.clusterIPs`, `.spec.clusterIP` is set to the IPv6 address because that is the first element in the `.spec.clusterIPs` array, overriding the default. </ins> {{% code_sample file="service/networking/dual-stack-preferred-ipfamilies-svc.yaml" %}}

1. When dual-stack is enabled on a cluster, existing Services (whether `IPv4` or `IPv6`) are configured by the control plane to set `.spec.ipFamilyPolicy` to `SingleStack` and set `.spec.ipFamilies` to the address family of the existing Service. The existing Service cluster IP <del> will be stored in `.spec.ClusterIPs`. </del> <ins> will be stored in `.spec.clusterIPs`. </ins> {{% code_sample file="service/networking/dual-stack-default-svc.yaml" %}}

[headless Services](/docs/concepts/services-networking/service/#headless-services) with selectors are configured by the control plane to set `.spec.ipFamilyPolicy` to `SingleStack` and set `.spec.ipFamilies` to the address family of the first service cluster IP range (configured via the <del> `--service-cluster-ip-range` flag to the kube-apiserver) even though `.spec.ClusterIP` is set to </del> <ins> `--service-cluster-ip-range` flag to the kube-apiserver) even though `.spec.clusterIP` is set to </ins> `None`. {{% code_sample file="service/networking/dual-stack-default-svc.yaml" %}}

1. To change a Service from dual-stack to single-stack, change `.spec.ipFamilyPolicy` from `PreferDualStack` or `RequireDualStack` to `SingleStack`. When you change this Service from <del> dual-stack to single-stack, Kubernetes retains only the first element in the `.spec.ClusterIPs` array, and sets `.spec.ClusterIP` to that IP address and sets `.spec.ipFamilies` to the address family of `.spec.ClusterIPs`. </del> <ins> dual-stack to single-stack, Kubernetes retains only the first element in the `.spec.clusterIPs` array, and sets `.spec.clusterIP` to that IP address and sets `.spec.ipFamilies` to the address family of `.spec.clusterIPs`. </ins> ### Headless Services without selector