makefile: enforce SSH tunnel IPv4 usage

Signed-off-by: Paulo Pires <pires@mesosphere.io>
mesosphere · Oct 4, 2017 · ec5ba64 · ec5ba64
1 parent 5c335c7
commit ec5ba64
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/Makefile b/Makefile
@@ -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)
 

diff --git a/README.md b/README.md
@@ -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: