update echo-server image and add ingress step

Author: spowelljr

site/content/en/docs/handbook/accessing.md

@@ -41,7 +41,7 @@ Services of type `NodePort` can be exposed via the `minikube service <service-na
 1. Create a Kubernetes deployment
 
     ```shell
-    kubectl create deployment hello-minikube1 --image=k8s.gcr.io/echoserver:1.4
+    kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0
     ```
 
 2. Create a Kubernetes service type NodePort
@@ -159,7 +159,7 @@ Services of type `LoadBalancer` can be exposed via the `minikube tunnel` command
 2. Create a Kubernetes deployment
 
     ```shell
-    kubectl create deployment hello-minikube1 --image=k8s.gcr.io/echoserver:1.4
+    kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0
     ```
 
 3. Create a Kubernetes service with type LoadBalancer

site/content/en/docs/handbook/deploying.md

@@ -11,7 +11,7 @@ aliases:
 ## kubectl
 
 ```shell
-kubectl create deployment hello-minikube1 --image=k8s.gcr.io/echoserver:1.4
+kubectl create deployment hello-minikube1 --image=kicbase/echo-server:1.0
 kubectl expose deployment hello-minikube1 --type=LoadBalancer --port=8080
 ```
 

site/content/en/docs/handbook/kubectl.md

@@ -77,7 +77,7 @@ minikube kubectl -- get pods
 Creating a deployment inside kubernetes cluster
 
 ```shell
-minikube kubectl -- create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.4
+minikube kubectl -- create deployment hello-minikube --image=kicbase/echo-server:1.0
 ```
 
 Exposing the deployment with a NodePort service

site/content/en/docs/start/_index.md

@@ -676,6 +676,10 @@ NAME              CLASS   HOSTS   ADDRESS          PORTS   AGE
 example-ingress   nginx   *       <your_ip_here>   80      5m45s
 ```
 
+**Note for Docker Desktop Users:**
+<br>
+To get ingress to work you'll need to open a new terminal window and run `minikube tunnel` and in the following step use `0.0.0.0` in place of `<ip_from_above>`.
+
 Now verify that the ingress works
 ```shell
 $ curl <ip_from_above>/foo

site/content/en/docs/tutorials/ambassador_ingress_controller.md

@@ -56,7 +56,7 @@ this [post](https://blog.getambassador.io/new-kubernetes-1-18-extends-ingress-c3
 First, let's create a Kubernetes deployment and service which we will talk to via Ambassador.
 
 ```shell script
-kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.4
+kubectl create deployment hello-minikube --image=kicbase/echo-server:1.0
 kubectl expose deployment hello-minikube --port=8080
 ```
 
@@ -105,7 +105,7 @@ that maps a target backend service to a given host or prefix.
 
 Let's create another Kubernetes deployment and service that we will expose via Ambassador -
 ```shell script
-kubectl create deployment mapping-minikube --image=k8s.gcr.io/echoserver:1.4
+kubectl create deployment mapping-minikube --image=kicbase/echo-server:1.0
 kubectl expose deployment mapping-minikube --port=8080
 ```