docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update layer-7-routing.md

This commit is contained in:
paigehargrave 2019-02-25 18:32:44 -05:00 committed by GitHub
parent 3367a96037
commit d2b5d6cdbb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
ee/ucp/kubernetes/layer-7-routing.md
View File

@ -439,59 +439,3 @@ dockerdemo-ingress dockerdemo.app.docker.example.com 80 7d
Assuming you have already registered a DNS record for your application pointing to the external load-balancer fronting the `infra` nodes, you should be able to access your application using the URL.You can also scale the docker demo deployment to test how ingress correctly routes traffic to all the backend pods! Assuming you have already registered a DNS record for your application pointing to the external load-balancer fronting the `infra` nodes, you should be able to access your application using the URL.You can also scale the docker demo deployment to test how ingress correctly routes traffic to all the backend pods!
![dockerdemo.png](../images/ingress-deploy.png) ![dockerdemo.png](../images/ingress-deploy.png)
## Check your deployment
The `default-http-backend` provides a simple service that serves a 404 page
at `/` and serves 200 on the `/healthz` endpoint.
1. Navigate to the **Controllers** page and confirm that the
**default-http-backend** and **nginx-ingress-controller** objects are
scheduled.
> Scheduling latency
>
> It may take several seconds for the HTTP backend and the ingress controller's
> `Deployment` and `ReplicaSet` objects to be scheduled.
{: .important}
![](../images/deploy-ingress-controller-2.png){: .with-border}
2. When the workload is running, navigate to the **Load Balancers** page
and click the **ingress-nginx** service.
![](../images/deploy-ingress-controller-3.png){: .with-border}
3. In the details pane, click the first URL in the **Ports** section.
A new page opens, displaying `default backend - 404`.
## Check your deployment from the CLI
From the command line, confirm that the deployment is running by using
`curl` with the URL that's shown on the details pane of the **ingress-nginx**
service.
```bash
curl -I http://<ucp-ip>:<ingress port>/
```
This command returns the following result.
```
HTTP/1.1 404 Not Found
Server: nginx/1.13.8
```
Test the server's health ping service by appending `/healthz` to the URL.
```bash
curl -I http://<ucp-ip>:<ingress port>/healthz
```
This command returns the following result.
```
HTTP/1.1 200 OK
Server: nginx/1.13.8
```