Exposing stargate component in GKE

[hoangpham95]

Type of question
I have trouble with exposing stargate service with an external IP address in GKE.

What did you do?

1. Create an ingress and attach to the service with the following yaml:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-name
  annotations:
spec:
  defaultBackend:
    service:
      name: service-name
      port:
        number: 9042

However when describing the ingress, the address is empty.
2. Update the service with a static IP with
kubectl patch svc service-name -p '{"spec": {"externalIPs": ["some-ip"]}}'
but the service's external IP address is still missing.

Did you expect to see some different?

Environment

• Helm charts version
  version.BuildInfo{Version:"v3.11.0", GitCommit:"472c5736ab01133de504a826bd9ee12cbe4e7904", GitTreeState:"clean", GoVersion:"go1.19.5"}

[Miles-Garnsey]

Hi @hoangpham95, this is really a GKE ingress question more than a k8ssandra question, but I'm happy to try to help.

What protocols are you planning to run over your ingress? This will affect the type you need.

[adejanovski]

Hi @hoangpham95,

you may want to check these docs to figure out how to expose services externally in GKE.
One thing to note though, is that the Cassandra drivers will discover the coordinator nodes IPs and try to use them to connect to them directly.
Hence, the static IP address that you'll set for the service/ingress will only be used as contact point, but then the driver will try to connect directly to the pods IPs, so you'll want to make sure they are reachable from your client apps.