Editing NGINX-ingress (section)

== Kubernetes Ingress Controller ==
This ingress controller is also labeled as 'nginx', though it diverges in features from the 'official' version.  It
is, however, more flexible than the NGINX version  through its ability to route arbitrary ports to services, not just 80 and 443 using HTTP/HTTPS protocols.  This is done by specifying the map from port to service in a configMap (and adding the ports to the exposing service), which makes it less 'generic' than it should, and forces you to modify the base controller deployment instead of just providing the Ingress like it is supposed to work.  

This version of the ingress controller is housed in this [https://github.com/kubernetes/ingress-nginx github repo].

The manifest that deploys the ingress controller is in the file deploy/mandatory.yaml ... it creates everything needed including the namespace, RBAC stuff, default backend, and the controller deployment.  I added the --update-status parameter, just to see what happened, but that is the only change.

To expose the controller, you need to provide a LoadBalancer service:

<pre>kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx
  namespace: ingress-nginx
  labels:
    app: ingress-nginx
spec:
  externalTrafficPolicy: Local
  type: LoadBalancer
  selector:
    app: ingress-nginx
  ports:
  - name: http
    port: 80
    targetPort: http
  - name: https
    port: 443
    targetPort: https</pre>

One like this is included in deploy/provider/cloud-generic.yaml.

This needs to be done in the namespace of the controller (ingress-nginx) so it can select the controller ... but it will need to be modified if additional ports are proxied.

The repo for this controller is cloned into:
 /workspace/outside-repos/ingress-nginx