updated docs to use glooctl

Author: axhixh

docs/getting_started/aws/lambda.md

@@ -27,8 +27,7 @@
 
 1. Install Gloo:
 
-        kubectl apply \
-                  -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+        glooctl install kube
 
 
 1. Create a kubernetes secret with your AWS credentials:

docs/getting_started/kubernetes/1.md

@@ -11,8 +11,7 @@
 
 1. Gloo and Envoy deployed and running on Kubernetes:
 
-        kubectl apply \
-          -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+        glooctl install kube
 
 
 1. Next, deploy the Pet Store app to kubernetes:
@@ -25,10 +24,17 @@ Let's verify this:
 
         glooctl upstream get
         
-        default-petstore-8080
-        gloo-system-gloo-8081
-        gloo-system-ingress-8080
-        gloo-system-ingress-8443
+        +--------------------------------+------------+----------+-------------+
+        |              NAME              |    TYPE    |  STATUS  |  FUNCTION   |
+        +--------------------------------+------------+----------+-------------+
+        | default-petstore-8080          | kubernetes | Accepted | addPet      |
+        |                                |            |          | deletePet   |
+        |                                |            |          | findPetById |
+        |                                |            |          | findPets    |
+        | gloo-system-control-plane-8081 | kubernetes | Accepted |             |
+        | gloo-system-ingress-8080       | kubernetes | Accepted |             |
+        | gloo-system-ingress-8443       | kubernetes | Accepted |             |
+        +--------------------------------+------------+----------+-------------+
 
     The upstream we want to see is `default-petstore-8080`. Digging a little deeper,
     we can verify that Gloo's function discovery populated our upstream with 

docs/getting_started/kubernetes/2.md

@@ -6,7 +6,7 @@ Now that we've seen the traditional routing functionality of Gloo (i.e. API-to-s
 
 Let's take a look at the upstream that was created for our petstore service:
 
-         glooctl upstream get default-petstore-8080
+         glooctl upstream get default-petstore-8080 -o yaml
          
          functions:
          - name: addPet

docs/installation/kubernetes.md

@@ -16,8 +16,7 @@
 Once your Kubernetes cluster is up and running, run the following command to deploy Gloo and Envoy to the `gloo-system` namespace:
 
 ```bash
-kubectl apply \
-  --filename https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+glooctl install kube 
 ```
 
 Check that the Gloo pods and services have been created:

docs/tutorials/fission.md

@@ -9,7 +9,7 @@ Setting up kubernetes: https://docs.fission.io/0.6.0/installation/kubernetessetu
 
 To install gloo, run:
 ```
-kubectl apply -f https://raw.githubusercontent.com/solo-io/gloo-install/master/kube/install.yaml
+glooctl install kube 
 ```
 
 # Deploy Function

docs/tutorials/openfaas.md

@@ -14,7 +14,7 @@ kubectl apply -f ./namespaces.yml,./yaml
 
 To install gloo, run:
 ```
-kubectl apply -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+glooctl install kube
 ```
 
 # Deploy Function

docs/tutorials/refactor_monolith.md

@@ -33,8 +33,7 @@ kubectl create clusterrolebinding permissive-binding \
 
 ## Install Gloo
 ```shell
-kubectl apply \
-          -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+glooctl install kube
 ```
 
 Wait \ Verify that all the pods are in Running status:

docs/tutorials/source_events_from_github.md

@@ -4,7 +4,7 @@ Sourcing Events from GitHub Webhooks
 ## Setup
 
 #### Deploy Gloo
-    kubectl apply -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+    glooctl install kube
 
 #### Deploy NATS and minio
     kubectl apply -f \

example/demo/README.md

@@ -31,8 +31,7 @@ kubectl create clusterrolebinding permissive-binding \
 
 ## Install Gloo
 ```shell
-kubectl apply \
-          -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+glooctl install kube
 ```
 
 Wait \ Verify that all the pods are in Running status:

example/grpc/README.md

@@ -20,8 +20,7 @@ minikube start
 
 ## Install Gloo
 ```shell
-kubectl apply \
-          -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+glooctl install kube
 ```
 
 Wait \ Verify that all the pods are in Running status:

example/source_events_from_github/README.md

@@ -8,7 +8,7 @@ Sourcing Events from GitHub Webhooks
 ## Setup
 
 #### Deploy Gloo
-    kubectl apply -f https://raw.githubusercontent.com/solo-io/gloo/master/install/kube/install.yaml
+    glooctl install kube
 
 #### Deploy NATS and minio
     kubectl apply -f \