External Name Support

[SeanRobb]

I would like to have a way to route traffic using ExternalName services and the ingress controller. The kubernetes/ingress-nginx project has solved this issue but I would like to use NGINX Plus to proxy this traffic.

I would like to see this project match the feature set for ExternalName services on the kubernetes/ingress-nginx project.

Thank you!

[Dean-Coakley]

Hi @SeanRobb

Thanks for the feature request.

External service support has been requested in this issue and is something that we are planning to implement. The considered implementation approach for NGINX OSS is laid out in this comment and for NGINX Plus we will use its re-resolving DNS names feature (the resolve parameter of the upstream server).

Are you using ExternalName services to route requests outside of the cluster or to the services inside the cluster but perhaps in a different namespace?

[SeanRobb]

Initially we would most like to see routing services outside of the cluster but we are also interested in the cross namespace routing.

Glad to hear that it is currently being planed. The re-resolving feature is a nice addition for NGINX Plus.

Thank you for the quick response.

[Dean-Coakley]

Alright, that's helpful to know.

For cross namespace routing:
You can use mergeable ingresses. So you can have a collection of 'minion-ingresses' defined across many namespaces that are merged into a single 'master-ingress' resource. Please see the example here.

Thank you!