Usage of `publishedService` in externalIP setup

Traefik Traefik v2
2

Ok, after some further digging I figured out what the other two keys in that group hostname and ip are doing: With both of them you can hardcode a domain or IP address to be published on all Ingresses.

So in my case I reconfigured it as follows:

providers:
  kubernetesIngress:
    ingressEndpoint:
      ip: 1.2.3.4

This way now the status of all Ingress is set and ArgoCD is able to do the health check on it.

This -- let's call it workaround -- has some downsides though. As you can see in my setup here I cannot configure both external IPs, for example.

I created a feature request for activating setting the status automatically also from ClusterIP and NodePort service on GitHub: Publish IPs from ClusterIP and NodePort services on Ingresses · Issue #7972 · traefik/traefik · GitHub

2 Likes