whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix Ingress callouts, links, nav, and templating (#12720)

Browse Source 
* Fix Ingress callouts, links, nav, and templating

* Update ingress.md

* Update ingress-minikube.md

* Delete .md that caused 404

* Delete .md that caused 404

* Update ingress-controllers.md

* Update ingress-minikube.md

* spell check pass

* Update ingress.md

* Update ingress-minikube.md
This commit is contained in:
Cody Clark
2019-02-27 15:15:30 -08:00
committed by Kubernetes Prow Robot
parent ab5e8c0d65
commit 0bbe2db0be
3 changed files with 65 additions and 109 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/access-application-cluster/ingress-minikube.md
+43 -52
View File
@@ -7,7 +7,7 @@ weight: 100
{{% capture overview %}}
An [Ingress](/docs/concepts/services-networking/ingress/) is an API object that defines rules which allow external access
to services in a cluster. An [Ingress controller](#) fulfills the rules set in the Ingress.
to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress.
{{< caution >}}
For the Ingress resource to work, the cluster **must** also have an Ingress controller running.
@@ -51,12 +51,10 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
kubectl get pods -n kube-system
```
{{< note >}}
This can take up to a minute.
{{< /note >}}
{{< note >}}This can take up to a minute.{{< /note >}}
Output:
```shell
NAME READY STATUS RESTARTS AGE
default-http-backend-59868b7dd6-xb8tq 1/1 Running 0 1m
@@ -118,10 +116,7 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
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:
@@ -130,8 +125,8 @@ This page shows you how to set up a simple Ingress which routes requests to Serv
Version: 1.0.0
Hostname: web-55b8c6998d-8k564
```
You can now access the sample app via the Minikube IP address and NodePort. The next step will let 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.
## Create an Ingress resource
@@ -140,32 +135,33 @@ The following file is an Ingress resource that sends traffic to your Service via
1. Create `example-ingress.yaml` from the following file:
```yaml
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: example-ingress
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
rules:
- host: hello-world.info
http:
paths:
- path: /*
backend:
serviceName: web
servicePort: 8080
```
```yaml
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: example-ingress
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
rules:
- host: hello-world.info
http:
paths:
- path: /*
backend:
serviceName: web
servicePort: 8080
```
1. Create the Ingress resrouce by running the following command:
1. Create the Ingress resource by running the following command:
```shell
kubectl apply -f example-ingress.yaml
```
Output:
```shell
ingress.extensions/example-ingress created
```
@@ -176,9 +172,7 @@ The following file is an Ingress resource that sends traffic to your Service via
kubectl get ingress
```
{{< note >}}
This can take a couple of minutes.
{{< /note >}}
{{< note >}}This can take a couple of minutes.{{< /note >}}
```shell
NAME HOSTS ADDRESS PORTS AGE
@@ -187,28 +181,27 @@ 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.
```shell
172.17.0.15 hello-world.info
```
```
172.17.0.15 hello-world.info
```
This sends requests from hello-world.info to Minikube.
1. Verify that the Ingress contorller is directing traffic:
1. Verify that the Ingress controller is directing traffic:
```shell
```shell
curl hello-world.info
````
```
Output:
```shell
Hello, world!
Version: 1.0.0
Hostname: web-55b8c6998d-8k564
```
{{< 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
@@ -239,12 +232,12 @@ The following file is an Ingress resource that sends traffic to your Service via
1. Edit the existing `example-ingress.yaml` and add the following lines:
```yaml
- path: /v2/*
backend:
serviceName: web2
servicePort: 8080
```
```yaml
- path: /v2/*
backend:
serviceName: web2
servicePort: 8080
```
1. Apply the changes:
@@ -285,16 +278,14 @@ The following file is an Ingress resource that sends traffic to your Service via
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 >}}
{{% /capture %}}
{{% capture whatsnext %}}
* Read more about [Ingress](/docs/concepts/services-networking/ingress/)
* Read more about [Ingress Controllers](#)
* Read more about [Ingress Controllers](/docs/concepts/services-networking/ingress-controllers/)
* Read more about [Services](/docs/concepts/services-networking/service/)
{{% /capture %}}