From ec1b074cac206a43f22893f7a3d7368fbada63e3 Mon Sep 17 00:00:00 2001 From: Kent 'picat' Gruber Date: Fri, 17 Jul 2020 15:05:22 -0400 Subject: [PATCH] Remove a potential for accidently running the SSH tunnels in server VM If a user is just clicking / copy-pasting, they could accidently think they next gcloud commands should be run inside the server VM. Removing that extra bit of information to make accessing the UIs as simple as possible. Moreover, the local commands on the cloud shell should just work without needing to SSH into the server VM. --- terraform/gcp/README.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/terraform/gcp/README.md b/terraform/gcp/README.md index dc780f522..6b4e22346 100644 --- a/terraform/gcp/README.md +++ b/terraform/gcp/README.md @@ -215,18 +215,6 @@ terraform apply -auto-approve -var="project=${GOOGLE_PROJECT}" -var="credentials ## Access the Cluster -You can now access the cluster using [SSH](https://en.wikipedia.org/wiki/Secure_Shell) in several ways. - -### SSH - -Use `gcloud` to SSH into one of the servers to run `nomad`, `consul`, or `vault` commands: - -```console -gcloud compute ssh hashistack-server-0 --zone=us-east1-c --tunnel-through-iap -``` - -### SSH Tunnel with Cloud Shell Web Preview - To access the Nomad, Consul, or Vault web UI inside the cluster, create an [SSH tunnel](https://cloud.google.com/community/tutorials/ssh-tunnel-on-gce) using `gcloud`. To open up tunnels to *all* of the UIs available in the cluster, run these commands which will start each SSH tunnel as a background process in your current shell: ```console @@ -247,6 +235,7 @@ If you're **not** using Cloud Shell, you can use any of these links: * [Vault](http://127.0.0.1:8200) * [Consul](http://127.0.0.1:8500) + ## Next Steps Click [here](https://github.com/hashicorp/nomad/blob/master/terraform/README.md#test) for next steps.