NGINX Ingress Controller

DEPRECATED see Using Ingress Controller with SCF

Introduction

NGINX Ingress Controller is one of the Kubernetes supported ingress controllers. Ingress controller is a special type of controller in the sense that it processes Kubernetes resources (the Ingress resource) and also controls the HTTP and HTTPS traffic, load-balancing or proxying the requests to one or more backend servers.

Learn how to use the NGINX Ingress Controller with CAP below.

Setting up NGINX Ingress Controller

WIP

Setting up CAP to use the NGINX Ingress Controller

To make all traffic go through the NGINX Ingress Controller, the CAP public services should not receive an external IP. In order to accomplish that, don't set the kube.external_ips property on helm install, and set the following:

• For UAA charts:

--set "services.ingress.class=nginx"
--set "services.ingress.backends.uaa.port=2793"
--set "env.UAA_PUBLIC_PORT=443" # Used to report the UAA port to the cf CLI.

• For CF charts:

--set "services.ingress.class=nginx"
--set "services.ingress.backends.router.port=443"
--set "env.UAA_PORT=443"

Post-deployment certificate management

WIP