Be able to limit nginx ingresses to a specific entrypoint(s)

[ajacques]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

I have deployed Traefik and added several custom TCP entrypoints (e.g. imap, pop3) to proxy to a TCP backend. I enabled the kubernetesNginxIngress provider, but now all my ingresses are being exposed on my custom TCP entrypoints (as per the Traefik dashboard.)

I would like the ability to limit the NGINX ingress to a specific entry point to make it easier to migrate to Traefik.

I attempted to add the traefik.ingress.kubernetes.io/router.entrypoints=web,websecure annotation to the ingress, however it had no effect until I changed the ingress class to traefik. I'd be happy to send a pull request if this is an acceptable change

[ajacques]

I see two options:

1. Set the default entrypoints at the provider level. e.g. --providers.kubernetesingressnginx.entrypoints=web,websecure
2. Set an Ingress-level annotation. e.g traefik.ingress.kubernetes.io/router.entrypoints or nginx.ingress.kubernetes.io/traefik.entrypoints

I propose to add support for the KubernetesIngressNginx provider to look at the traefik.ingress.kubernetes.io/router.entrypoints annotation and filter the entrypoints for that ingress. This will make it easy for users who are migrating because then the same annotation applies if/when they change their ingress class from nginx to traefik.

WIP Implementation: https://github.com/traefik/traefik/compare/master...ajacques:traefik:master?expand=1

[kevinpollet]

Hello @ajacques and thanks for opening this,

During our triage session, we discussed this topic and agreed that we would prefer to mimic what ingress-nginx does (there is two flags allowing to configure the http and https port, see https://kubernetes.github.io/ingress-nginx/user-guide/cli-arguments/) and add configuration options at the provider level. These new options would allow to configure the http and https entrypoints.

[ajacques]

Just to confirm I understand what you're looking for. Do you mean something like this:

 --providers.kubernetesingressnginx
 --providers.kubernetesingressnginx.controllerclass=k8s.io/ingress-nginx
 --providers.kubernetesingressnginx.ingressclass=nginx
+--providers.kubernetesingressnginx.http-entrypoint=web
+--providers.kubernetesingressnginx.https-entrypoint=websecure

[ajacques]

I just submitted a new pull request with those requested changes: #12727