kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Revise task for practising NGINX Ingress controller

pull/29206/head
Tim Bannister 2021-08-03 14:33:43 +01:00
parent 85d3fb9900
commit 9d77a6bf22
1 changed files with 135 additions and 150 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

285
content/en/docs/tasks/access-application-cluster/ingress-minikube.md
View File

@ -2,6 +2,7 @@
title: Set up Ingress on Minikube with the NGINX Ingress Controller title: Set up Ingress on Minikube with the NGINX Ingress Controller
content_type: task content_type: task
weight: 100 weight: 100
min-kubernetes-server-version: 1.19
--- ---
<!-- overview --> <!-- overview -->
@ -17,23 +18,21 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
If you are using an older Kubernetes version, switch to the documentation
for that version.
### Create a Minikube cluster
Using Katacoda
: {{< kat-button >}}
Locally
: If you already [installed Minikube](/docs/tasks/tools/#minikube)
locally, run `minikube start` to create a cluster.
<!-- steps --> <!-- steps -->
## Create a Minikube cluster
1. Click **Launch Terminal**
{{< kat-button >}}
1. (Optional) If you installed Minikube locally, run the following command:
```shell
minikube start
```
## Enable the Ingress controller ## Enable the Ingress controller
1. To enable the NGINX Ingress controller, run the following command: 1. To enable the NGINX Ingress controller, run the following command:
@ -45,14 +44,14 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
1. Verify that the NGINX Ingress controller is running 1. Verify that the NGINX Ingress controller is running
{{< tabs name="tab_with_md" >}} {{< tabs name="tab_with_md" >}}
{{% tab name="minikube v1.19 or later" %}} {{% tab name="minikube v1.19 or later" %}}
```shell ```shell
kubectl get pods -n ingress-nginx kubectl get pods -n ingress-nginx
``` ```
{{< note >}}This can take up to a minute.{{< /note >}} {{< note >}}It can take up to a minute before you see these pods running OK.{{< /note >}}
Output: The output is similar to:
``` ```
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
@ -60,15 +59,14 @@ ingress-nginx-admission-create-g9g49 0/1 Completed 0 11m
ingress-nginx-admission-patch-rqp78 0/1 Completed 1 11m ingress-nginx-admission-patch-rqp78 0/1 Completed 1 11m
ingress-nginx-controller-59b45fb494-26npt 1/1 Running 0 11m ingress-nginx-controller-59b45fb494-26npt 1/1 Running 0 11m
``` ```
{{% /tab %}} {{% /tab %}}
{{% tab name="minikube v1.18.1 or earlier" %}}
{{% tab name="minikube v1.18.1 or earlier" %}}
```shell ```shell
kubectl get pods -n kube-system kubectl get pods -n kube-system
``` ```
{{< note >}}This can take up to a minute.{{< /note >}} {{< note >}}It can take up to a minute before you see these pods running OK.{{< /note >}}
Output: The output is similar to:
``` ```
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
@ -79,133 +77,121 @@ kubernetes-dashboard-5498ccf677-b8p5h 1/1 Running 0 2m
nginx-ingress-controller-5984b97644-rnkrg 1/1 Running 0 1m nginx-ingress-controller-5984b97644-rnkrg 1/1 Running 0 1m
storage-provisioner 1/1 Running 0 2m storage-provisioner 1/1 Running 0 2m
``` ```
{{% /tab %}}
{{< /tabs >}}
```shell
kubectl get pods -n ingress-nginx
```
{{< note >}}This can take up to a minute.{{< /note >}}
Output:
```shell
NAME READY STATUS RESTARTS AGE
ingress-nginx-admission-create-2tgrf 0/1 Completed 0 3m28s
ingress-nginx-admission-patch-68b98 0/1 Completed 0 3m28s
ingress-nginx-controller-59b45fb494-lzmw2 1/1 Running 0 3m28s
```
Make sure that you see a Pod with a name that starts with `nginx-ingress-controller-`.
{{% /tab %}}
{{< /tabs >}}
## Deploy a hello, world app ## Deploy a hello, world app
1. Create a Deployment using the following command: 1. Create a Deployment using the following command:
```shell ```shell
kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0 kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0
``` ```
Output: The output should be:
```shell ```
deployment.apps/web created deployment.apps/web created
``` ```
1. Expose the Deployment: 1. Expose the Deployment:
```shell ```shell
kubectl expose deployment web --type=NodePort --port=8080 kubectl expose deployment web --type=NodePort --port=8080
``` ```
Output: The output should be:
```shell ```
service/web exposed service/web exposed
``` ```
1. Verify the Service is created and is available on a node port: 1. Verify the Service is created and is available on a node port:
```shell ```shell
kubectl get service web kubectl get service web
``` ```
Output: The output is similar to:
```shell ```
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
web NodePort 10.104.133.249 <none> 8080:31637/TCP 12m web NodePort 10.104.133.249 <none> 8080:31637/TCP 12m
``` ```
1. Visit the service via NodePort: 1. Visit the Service via NodePort:
```shell ```shell
minikube service web --url minikube service web --url
``` ```
Output: The output is similar to:
```shell ```
http://172.17.0.15:31637 http://172.17.0.15:31637
``` ```
{{< note >}}Katacoda environment only: at the top of the terminal panel, click the plus sign, and then click **Select port to view on Host 1**. Enter the NodePort, in this case `31637`, and then click **Display Port**.{{< /note >}} {{< note >}}Katacoda environment only: at the top of the terminal panel, click the plus sign, and then click **Select port to view on Host 1**. Enter the NodePort, in this case `31637`, and then click **Display Port**.{{< /note >}}
Output: The output is similar to:
```shell ```
Hello, world! Hello, world!
Version: 1.0.0 Version: 1.0.0
Hostname: web-55b8c6998d-8k564 Hostname: web-55b8c6998d-8k564
``` ```
You can now access the sample app via the Minikube IP address and NodePort. The next step lets you access You can now access the sample app via the Minikube IP address and NodePort. The next step lets you access
the app using the Ingress resource. the app using the Ingress resource.
## Create an Ingress resource ## Create an Ingress
The following file is an Ingress resource that sends traffic to your Service via hello-world.info. The following manifest defines an Ingress that sends traffic to your Service via hello-world.info.
1. Create `example-ingress.yaml` from the following file: 1. Create `example-ingress.yaml` from the following file:
{{< codenew file="service/networking/example-ingress.yaml" >}} {{< codenew file="service/networking/example-ingress.yaml" >}}
1. Create the Ingress resource by running the following command: 1. Create the Ingress object by running the following command:
```shell ```shell
kubectl apply -f https://k8s.io/examples/service/networking/example-ingress.yaml kubectl apply -f https://k8s.io/examples/service/networking/example-ingress.yaml
``` ```
Output: The output should be:
```shell ```
ingress.networking.k8s.io/example-ingress created ingress.networking.k8s.io/example-ingress created
``` ```
1. Verify the IP address is set: 1. Verify the IP address is set:
```shell ```shell
kubectl get ingress kubectl get ingress
``` ```
{{< note >}}This can take a couple of minutes.{{< /note >}} {{< note >}}This can take a couple of minutes.{{< /note >}}
```shell You should see an IPv4 address in the ADDRESS column; for example:
NAME CLASS HOSTS ADDRESS PORTS AGE
example-ingress <none> hello-world.info 172.17.0.15 80 38s
```
1. Add the following line to the bottom of the `/etc/hosts` file. ```
NAME CLASS HOSTS ADDRESS PORTS AGE
example-ingress <none> hello-world.info 172.17.0.15 80 38s
```
{{< 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 >}} 1. Add the following line to the bottom of the `/etc/hosts` file on
your computer (you will need adminstrator access):
``` ```
172.17.0.15 hello-world.info 172.17.0.15 hello-world.info
``` ```
This sends requests from hello-world.info to Minikube. {{< 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 >}}
After you make this change, your web browser sends requests for
hello-world.info URLs to Minikube.
1. Verify that the Ingress controller is directing traffic: 1. Verify that the Ingress controller is directing traffic:
@ -213,9 +199,9 @@ The following file is an Ingress resource that sends traffic to your Service via
curl hello-world.info curl hello-world.info
``` ```
Output: You should see:
```shell ```
Hello, world! Hello, world!
Version: 1.0.0 Version: 1.0.0
Hostname: web-55b8c6998d-8k564 Hostname: web-55b8c6998d-8k564
@ -223,34 +209,35 @@ The following file is an Ingress resource that sends traffic to your Service via
{{< note >}}If you are running Minikube locally, you can visit hello-world.info from your browser.{{< /note >}} {{< note >}}If you are running Minikube locally, you can visit hello-world.info from your browser.{{< /note >}}
## Create Second Deployment ## Create a second Deployment
1. Create a v2 Deployment using the following command: 1. Create another Deployment using the following command:
```shell ```shell
kubectl create deployment web2 --image=gcr.io/google-samples/hello-app:2.0 kubectl create deployment web2 --image=gcr.io/google-samples/hello-app:2.0
``` ```
Output: The output should be:
```shell ```
deployment.apps/web2 created deployment.apps/web2 created
``` ```
1. Expose the Deployment: 1. Expose the second Deployment:
```shell ```shell
kubectl expose deployment web2 --port=8080 --type=NodePort kubectl expose deployment web2 --port=8080 --type=NodePort
``` ```
Output: The output should be:
```shell ```
service/web2 exposed service/web2 exposed
``` ```
## Edit Ingress ## Edit the existing Ingress {#edit-ingress}
1. Edit the existing `example-ingress.yaml` and add the following lines: 1. Edit the existing `example-ingress.yaml` manifest, and add the
following lines at the end:
```yaml ```yaml
- path: /v2 - path: /v2
@ -264,47 +251,47 @@ The following file is an Ingress resource that sends traffic to your Service via
1. Apply the changes: 1. Apply the changes:
```shell ```shell
kubectl apply -f example-ingress.yaml kubectl apply -f example-ingress.yaml
``` ```
Output: You should see:
```shell ```
ingress.networking/example-ingress configured ingress.networking/example-ingress configured
``` ```
## Test Your Ingress ## Test your Ingress
1. Access the 1st version of the Hello World app. 1. Access the 1st version of the Hello World app.
```shell ```shell
curl hello-world.info curl hello-world.info
``` ```
Output: The output is similar to:
```shell ```
Hello, world! Hello, world!
Version: 1.0.0 Version: 1.0.0
Hostname: web-55b8c6998d-8k564 Hostname: web-55b8c6998d-8k564
``` ```
1. Access the 2nd version of the Hello World app. 1. Access the 2nd version of the Hello World app.
```shell ```shell
curl hello-world.info/v2 curl hello-world.info/v2
``` ```
Output: The output is similar to:
```shell ```
Hello, world! Hello, world!
Version: 2.0.0 Version: 2.0.0
Hostname: web2-75cd47646f-t8cjk Hostname: web2-75cd47646f-t8cjk
``` ```
{{< note >}}If you are running Minikube locally, you can visit hello-world.info and hello-world.info/v2 from your browser.{{< /note >}} {{< note >}}If you are running Minikube locally, you can visit hello-world.info and hello-world.info/v2 from your browser.{{< /note >}}
@ -315,5 +302,3 @@ The following file is an Ingress resource that sends traffic to your Service via
* Read more about [Ingress Controllers](/docs/concepts/services-networking/ingress-controllers/) * Read more about [Ingress Controllers](/docs/concepts/services-networking/ingress-controllers/)
* Read more about [Services](/docs/concepts/services-networking/service/) * Read more about [Services](/docs/concepts/services-networking/service/)