Thank you for all the suggestions..
I tried to setup a public ssh-key at the project level, but I'm unable to make it work, I can't ssh a GCE from another one with the private key.
The key is visible at the console, but I can't see how the target server take the key into account.
returns a 404.
Jason,
it's very interresting, but it does not work as I expect.
I have
- a host project sharing VPCs. Theses VPCs all use a Palo Alto Firewall GCP appliance as default GW. This FW filter trafic between GCP and our on premise datacenter
- the VM Bastion is connected to one of the shared VPC called the Management VPC
- a target VM : instance-1 is connected to another shared VPC called the developpment VPC
- there are other shared VPC like production VPC, still using Palot Alto FW GCP appliance as default GW
- the VPC are not peered
1. The command to enter from the bastion is : gcloud beta compute ssh instance-1 --internal-ip
But it answers : The resource 'projects/pocbastion-xxxxx/zones/europe-west1-b/instances/instance-1' was not found
==> We have a GCP project for each application in GCP and there is only one bastion. So gcloud beta compute ssh command should allow to specify the GCP project of the target server
2. Our VPC are not peered for network isolation, so this way is not applicable in our case.
Thanks
MLD