Skip to content

Commit

Permalink
makefile: enforce SSH tunnel IPv4 usage
Browse files Browse the repository at this point in the history
Signed-off-by: Paulo Pires <pires@mesosphere.io>
  • Loading branch information
pires committed Oct 4, 2017
1 parent 5c335c7 commit ec5ba64
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ endef

kubectl-tunnel: $(ID_FILE)
$(call get_master_ip)
ssh -i $(ID_FILE) -f -o "UserKnownHostsFile=/dev/null" -o "StrictHostKeyChecking=no" -o "ServerAliveInterval=120" \
ssh -i $(ID_FILE) -4 -f -o "UserKnownHostsFile=/dev/null" -o "StrictHostKeyChecking=no" -o "ServerAliveInterval=120" \
-N -L 9000:apiserver-insecure.kubernetes.l4lb.thisdcos.directory:9000 \
$(SSH_USER)@$(MASTER_IP)

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ In order to access the Kubernetes API from outside the DC/OS cluster, one needs
On a terminal window, run:

```bash
ssh -N -L 9000:apiserver-insecure.kubernetes.l4lb.thisdcos.directory:9000 <USER>@<HOST>
ssh -4 -N -L 9000:apiserver-insecure.kubernetes.l4lb.thisdcos.directory:9000 <USER>@<HOST>
```

When the Kubernetes API task(s) are healthy, it should be accessible on `http://localhost:9000`. Reaching this endpoint should show something like this:
Expand Down

0 comments on commit ec5ba64

Please sign in to comment.