Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add hint to kubernetes-auto-discovery.adoc regarding DNS discovery #1504

Open
wants to merge 2 commits into
base: v/5.5
Choose a base branch
from
Open

Add hint to kubernetes-auto-discovery.adoc regarding DNS discovery #1504

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b60febb
Add hing to kubernetes-auto-discovery.adoc regarding DNS discovery
holgerstolzenberg Jan 28, 2025
435bcd4
Merge branch 'v/5.5' into patch-1
holgerstolzenberg Feb 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/modules/kubernetes/pages/kubernetes-auto-discovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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].