History

zoues be05d403ac fix vts readme		2017-03-21 23:35:43 +08:00
..
default-backend.yaml	add custom vts metrics example	2017-03-21 23:29:57 +08:00
nginx-ingress-controller.yaml	add custom vts metrics example	2017-03-21 23:29:57 +08:00
nginx-vts-metrics-conf.yaml	add custom vts metrics example	2017-03-21 23:29:57 +08:00
README.md	fix vts readme	2017-03-21 23:35:43 +08:00

README.md

Deploying the Nginx Ingress controller

This example aims to demonstrate the deployment of an nginx ingress controller and use a ConfigMap to enable nginx vts module and export metrics for prometheus.

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:

$ 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

Custom configuration

$ cat nginx-vts-metrics-conf.yaml
apiVersion: v1
data:
  enable-vts-status: "true"
kind: ConfigMap
metadata:
  name: nginx-vts-metrics-conf
  namespace: kube-system

$ kubectl create -f nginx-vts-metrics-conf.yaml

Controller

You can deploy the controller as follows:

$ 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

Result

Check the contents of the configmap is present in the nginx.conf file using: kubectl exec nginx-ingress-controller-873061567-4n3k2 -n kube-system curl localhost:10254/metrics