Add hing to kubernetes-auto-discovery.adoc regarding DNS discovery

docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc

@@ -51,6 +51,12 @@ kind: Service
 metadata:
   name: MY-SERVICE-NAME
 spec:
+  # In some rare special cases (embedded mode with min cluster size matching replica count) your initial deployment might run into a hen-egg problem.
+  # It is caused by Kubernetes DNS only resolving headless service´s when the underlying pods are healthy (or ready).
+  # If your pods need the service to be resolved before, the property `publishNotReadyAddresses` comes in handy.
+  # Please also refer to [Kubernetes Service](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#service-v1-core) spec.
+  # 
+  # publishNotReadyAddresses: true
   type: LoadBalancer
   selector:
     app: APP-NAME
@@ -348,4 +354,4 @@ For the complete example, please check link:https://guides.hazelcast.org/kuberne
 
 If your Hazelcast cluster is deployed on Kubernetes, but your Hazelcast client is in a completely different network, then it can connect only through the public Internet. This requires exposing each Hazelcast member pod with a dedicated NodePort or LoadBalancer Kubernetes service. For details and a complete example, please check link:https://guides.hazelcast.org/kubernetes-external-client/[Hazelcast Guides: Connect External Hazelcast Client to Kubernetes].
 
-NOTE: For information on configuring persistence in Kubernetes environments, see xref:kubernetes:kubernetes-persistence.adoc[Running Hazelcast {enterprise-product-name} with Persistence under Kubernetes].
+NOTE: For information on configuring persistence in Kubernetes environments, see xref:kubernetes:kubernetes-persistence.adoc[Running Hazelcast {enterprise-product-name} with Persistence under Kubernetes].