From 387c8c20250dabfe969350e3cf08206696affbb2 Mon Sep 17 00:00:00 2001 From: Jack Date: Thu, 21 Sep 2023 14:56:32 +0100 Subject: [PATCH] Update spelling of "hazelcast" (#851) --- docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc b/docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc index 1cc4338b4..2bb429488 100644 --- a/docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc +++ b/docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc @@ -345,7 +345,7 @@ For the complete example, please check link:https://guides.hazelcast.org/kuberne === Outside Kubernetes Cluster -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 Hazelast 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]. +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]. == Running Hazelcast Enterprise with Persistence under Kubernetes [.enterprise]*Enterprise*