exposing Cassandra causes pool creation error
Opened this issue · 1 comments
Hi,
I have set up Cassandra on Kubernetes, and i am trying to expose it on a public port to make it accessible to external applications that resides on a different server.
I have used the NodePort type of service which exposes the service on port 300xxx. However, when i create a session with Cassandra it connects correctly to the service, but then when trying to add Cassandra nodes to the pool it tries to connect them on the 300xxx port instead of the 9042 one.
What would be the most appropriate solution to expose Cassandra on a Kubernetes cluster?
I was thinking to use a load balacer service, but it seems that it only suits services that resides on public cloud providers. Another solution i was thinking of is to put a nginx server that handles the requests.
It seems that the port isn't the only problem as even exposing the service with a LoadBalancer the other Cassandra nodes are not reachable. This means that any connection to Cassandra must be made within the cluster (to be able to reach the other nodes). Has anyone had this issue?