From 8e06b116f900f804589cfd85808e7da4cdb232ce Mon Sep 17 00:00:00 2001
From: Prashanth Balasubramanian <beeps@google.com>
Date: Fri, 25 Mar 2016 18:08:55 -0700
Subject: [PATCH] Update firewall rule docs.

---
 docs/user-guide/ingress.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md
index 18d8add185..9fc838eb35 100644
--- a/docs/user-guide/ingress.md
+++ b/docs/user-guide/ingress.md
@@ -52,12 +52,9 @@ l7-lb-controller-v0.6.0-chnan   2/2       Running   0          1d
 Make sure you review the [beta limitations](https://github.com/kubernetes/contrib/tree/master/ingress/controllers/gce/BETA_LIMITATIONS.md) of this controller. In particular, you need to create a single firewall-rule on your cloudprovider, to allow health checks. On GKE this would be:
 
 ```shell
-$ export TAG=$(basename `gcloud container clusters describe ${CLUSTER_NAME} --zone ${ZONE} | grep gke | awk '{print $2}'` | sed -e s/group/node/)
-$ export NODE_PORT=$(kubectl get -o jsonpath="{.spec.ports[0].nodePort}" services echoheaders)
 $ gcloud compute firewall-rules create allow-130-211-0-0-22 \
   --source-ranges 130.211.0.0/22 \
-  --target-tags $TAG \
-  --allow tcp:$NODE_PORT
+  --allow tcp:30000-32767
 ```
 
 In environments other than GCE/GKE, you need to [deploy a controller](https://github.com/kubernetes/contrib/tree/master/ingress/controllers) as a pod.