Update modules/ROOT/pages/clustering/setup/discovery.adoc

Co-authored-by: NataliaIvakina <[email protected]>

Author: renetapopova

modules/ROOT/pages/clustering/setup/discovery.adoc

@@ -190,7 +190,7 @@ The following settings are used to configure for this scenario:
 * Set `dbms.cluster.discovery.resolver_type=K8S`.
 * Set `xref:configuration/configuration-settings.adoc#config_dbms.kubernetes.label_selector[dbms.kubernetes.label_selector]` to the label selector for the cluster services.
 For more information, see the https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors[Kubernetes official documentation^].
-* Set xref:configuration/configuration-settings.adoc#config_dbms.kubernetes.discovery.service_port_name[`dbms.kubernetes.discovery.service_port_name]` to the name of the service port used in the Kubernetes service definition for the Core's discovery port.
+* Depending on your discovery service version, set either `xref:configuration/configuration-settings.adoc#config_dbms.kubernetes.service_port_name[dbms.kubernetes.service_port_name]` (v1), or xref:configuration/configuration-settings.adoc#config_dbms.kubernetes.discovery.v2.service_port_name[`dbms.kubernetes.discovery.v2.service_port_name]` (v2) to the name of the service port used in the Kubernetes service definition for the Core's discovery port.
 For more information, see the https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/[Kubernetes official documentation^].
 
 With this configuration, `dbms.cluster.discovery.endpoints` is not used and any value assigned to it is ignored.