You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"}
The text was updated successfully, but these errors were encountered:
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.
Type of question
I have trouble with exposing stargate service with an external IP address in GKE.
What did you do?
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
version.BuildInfo{Version:"v3.11.0", GitCommit:"472c5736ab01133de504a826bd9ee12cbe4e7904", GitTreeState:"clean", GoVersion:"go1.19.5"}
The text was updated successfully, but these errors were encountered: