Lokomotive: Nginx Ingress Controller as an alternative to Contour

[ipochi]

Currently Ingress component category in Lokomotive has only one implementation of Contour. It would be nice to have an alternative component such as Nginx Ingress controller.

[surajssd]

Are there any specific issues you see with contour that will be addressed by nginx?

[invidian]

Are there any specific issues you see with contour that will be addressed by nginx?

e.g. propagation of Load Balancer IP address to Ingress object, which is not working in Contour (https://github.com/projectcontour/contour/issues/403)

[surajssd]

If that’s the case and if we move ahead with shipping and supporting two ingress providers then we also need to figure out how do we switch ingress class annotation seamlessly in the ingress configuration we ship without having the user to specify that.

[ipochi]

@invidian @surajssd

Now that one of the limitation in Contour was fixed upstream. and since we haven't really decided(mostly don't want to) of supporting alternate components per category. I am of the opinion we close this.

[surajssd]

Lets open it when we need it.

[invidian]

Closing then.