Try to create a Cloud NAT router on the same network you are creating the cluster and recreate the cluster.
After this, try to install Istio again.
Is possible that Istio is not able to get the images for some components because the cluster is not able to access internet.
Cloud NAT on GCP
Router redundancy protocol like VRRP or CARP. Which are virtual routers that coordinate which physical host will respond to neighbor discovery. In other words, clustering methods for a virtual IP address.
Dynamic routing protocols are also possible. However, it can be an operational challenge to get hosts to speak your IGP.
Providing the network as one IP of the home edge router assumes NAT is being used. This will not be true for IPv6, where each device is uniquely addressed. In which case you would want to provide the prefix of your net, possibly size /56.
It is unclear from your diagram what 60.XX.XX.1 is.
Don't obfuscate IP address, use real ones, or the documentation ...
You're actually forgetting about a third option: a VPN.
Instead of giving your router's public IP which changes when you restart the router, you could use a VPN service with a static IP or host your own VPN service on a server with a static IP.
That way you don't have to inform IT every time your IP changes.
Should I Give my "Router's Public IP (60.XX.XX.20)"?- But If I give
this, Restarting my router is changing the Public IP. So no use of
giving this IP.
Yes. When and if your router ip address changes give your IT group the new ip address.
Should I give gateway to my "Router's Public IP (60.XX.XX.1)"? - This,
I am assuming that the gateway of the "...
You want to connect from the ESXi console to another system.
Do you have opened the firewall on the host for this connections?
Look in "Configuration -> Security Profile" if your connection is opened. e.G. SSH Client is normally blocked.
Additionally you must have a static route on your ESXi host for the guest OS network if the gateway VM is not your ...
ip route show 0/0
ip route show 0.0.0.0/0
ip route show 0.0.0.0/0.0.0.0
ip -f inet route show default
ip -4 route show default
Versions I tested treated 'ip route show' and 'ip route list' as equivalents (not the case with 'ip route get')
There's an explanation at https://bugzilla.kernel.org/show_bug.cgi?id=197899
If I understand it ...
I now have it working. I use Pritunl rather than pure OpenVPN.
My VPN server has a single NAT route to 0.0.0.0/0
VPC1 (172.31.0.0/16) - Transit gateway and my VPN server
VPC2 (184.108.40.206/16) - Another VPC attached to the transit gateway
Both VPC's are already attached to the TG
In each VPC add a route in your subnet route tables for the other VPC CIDR ...