Kubernetes API discovery across namespaces #24684
Closed
felipeheld
started this conversation in
General
Replies: 1 comment 4 replies
-
Hello, @felipeheld! We do not support multi-namespace discovery. This is done on purpose since, usually, the discovery is via K8s services, which do not support multi-namespaces. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When using Hazecast in its embedded topology and Hazelcast's Kubernetes's API for node discovery I believe it is not possible for nodes to discover one another across namespaces, given only one service name and one namespace definition are allowed in the discovery configuration.
The relevant code is here:
hazelcast/hazelcast/src/main/java/com/hazelcast/kubernetes/KubernetesClient.java
Lines 243 to 251 in 120d258
It would have been desirable in my case to have the endpoint be discoverable in more than one namespace, however I am not sure whether I'm actually right in my propositions nor if, were I right, this would be of actual use to other developers.
I'd be more than willing to create a PR, but I honestly believe it'd be better to just ask beforehand, just in case this is the intended behavior as deemed fit by the majority or by people more qualified in the project's development.
Beta Was this translation helpful? Give feedback.
All reactions