40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
# Deploying the Nginx Ingress controller
|
|
|
|
This example aims to demonstrate the deployment of an nginx ingress controller and
|
|
use a ConfigMap to configure a custom list of headers to be passed to the upstream
|
|
server
|
|
|
|
## Default Backend
|
|
|
|
The default backend is a Service capable of handling all url paths and hosts the
|
|
nginx controller doesn't understand. This most basic implementation just returns
|
|
a 404 page:
|
|
|
|
```console
|
|
$ kubectl apply -f default-backend.yaml
|
|
deployment "default-http-backend" created
|
|
service "default-http-backend" created
|
|
|
|
$ kubectl -n kube-system get po
|
|
NAME READY STATUS RESTARTS AGE
|
|
default-http-backend-2657704409-qgwdd 1/1 Running 0 28s
|
|
```
|
|
|
|
## Controller
|
|
|
|
You can deploy the controller as follows:
|
|
|
|
```console
|
|
$ kubectl apply -f nginx-ingress-controller.yaml
|
|
deployment "nginx-ingress-controller" created
|
|
|
|
$ kubectl -n kube-system get po
|
|
NAME READY STATUS RESTARTS AGE
|
|
default-http-backend-2657704409-qgwdd 1/1 Running 0 2m
|
|
nginx-ingress-controller-873061567-4n3k2 1/1 Running 0 42s
|
|
```
|
|
|
|
Note the default settings of this controller:
|
|
* serves a `/healthz` url on port 10254, as both a liveness and readiness probe
|
|
* takes a `--default-backend-service` argument pointing to the Service created above
|
|
|