From 4bc7a5f8b1f439d50e569072165057c0226a4867 Mon Sep 17 00:00:00 2001 From: James Woodall Date: Wed, 19 Jun 2019 20:56:18 +0100 Subject: [PATCH] Minikube IP Address fixup for ingress demonstration (#14906) * Updated IP Address for /etc/hosts Tested on Minikube for macOS. When using Minikube, the IP address listed in `kubectl get ingress` is the internal Minikube IP address and is not available on the web browser. Added advice to the user that when using Minikube, add the Minikube IP address to the Hosts file instead of the IP address displayed in `kubectl get ingress`. * Update ingress-minikube.md --- .../docs/tasks/access-application-cluster/ingress-minikube.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/tasks/access-application-cluster/ingress-minikube.md b/content/en/docs/tasks/access-application-cluster/ingress-minikube.md index 9408c34561..0335c0978c 100644 --- a/content/en/docs/tasks/access-application-cluster/ingress-minikube.md +++ b/content/en/docs/tasks/access-application-cluster/ingress-minikube.md @@ -178,6 +178,8 @@ The following file is an Ingress resource that sends traffic to your Service via 1. Add the following line to the bottom of the `/etc/hosts` file. + {{< note >}}If you are running Minikube locally, use `minikube ip` to get the external IP. The IP address displayed within the ingress list will be the internal IP.{{< /note >}} + ``` 172.17.0.15 hello-world.info ```