Hello Shubhanan,
I displayed the external IP address of the NAT gateway.
-- For public cluster i did use this documentation [1] to use the NAT Gateway with Kubernetes Engine and i was able to Verify the NAT gateway routing with the kubctl command:
kubectl run example -i -t --rm --restart=Never --image centos:7 -- curl -s http://ipinfo.io/ip
For private cluster you have to enable the Alias IPs [2] as it allow Pods to directly access hosted services without using a NAT gateway.
Cluster IPs for internal Services remain only available from within the cluster. If you want to access a Kubernetes Service from within the VPC, but from outside of the cluster (for example, from a Compute Engine instance), use an internal load balancer [3].
Did you enable Alias IPs?
Did you enable Alias IPs?
[1]https://cloud.google.com/solutions/using-a-nat-gateway-with-kubernetes-engine
[2]https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips
[3]https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/79811b01-79f9-4e36-846e-c61937fbaa8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment