kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-01 16:05:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Remove a potential for accidently running the SSH tunnels in server VM

Browse Source 
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.
This commit is contained in:
Kent 'picat' Gruber
2020-07-17 15:05:22 -04:00
parent 8e53650ebb
commit ec1b074cac
1 changed files with 1 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
terraform/gcp/README.md
View File

@@ -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.