You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For demo purposes, I have a K8s Deployment with a single replica, an associated Service and an Ingress manifest.
The service is reachable at the defined URL and the confguration (route and service) shows up in the traefik-ui as well.
When I scale down the deployment to 0 replicas (to simulate an outage or application problem), thus having an empty list of helthy endpoints in K8s, Traefik fully removes the whole config (at least from the UI, not even the route is visible) and traefik return a 404 response when the service is accessed.
I expected in this case, that an error "503 Service Unavailable" in this case, indicating that the requested service is known, but not available currently. IIRC, Traefik1 behaved that way, but I am not sure.
What did you see instead?
I got an error 404, as if the service is not configured at all, which is different from being configured and just not available.
According to #1688 and #1689 this is supposed to work for Kubernetes providers, but it seems that was lost in between, at least it seems to not work anymore for me. It seems in 2017 there was a EmptyBackendHandler middleware (from #1748) for this case, but I can't find that in the docs.
Ohmy, the docs just gave me that --providers.kubernetesingress.allowemptyservices: Allow creation of services without endpoints. (Default: false) does exist in the CLI args, too - so this might solve my issues.
Testing tomorrow. If so, sorry for the noise.
Welcome!
What did you do?
For demo purposes, I have a K8s Deployment with a single replica, an associated Service and an Ingress manifest.
The service is reachable at the defined URL and the confguration (route and service) shows up in the traefik-ui as well.
When I scale down the deployment to 0 replicas (to simulate an outage or application problem), thus having an empty list of helthy endpoints in K8s, Traefik fully removes the whole config (at least from the UI, not even the route is visible) and traefik return a 404 response when the service is accessed.
I expected in this case, that an error "503 Service Unavailable" in this case, indicating that the requested service is known, but not available currently. IIRC, Traefik1 behaved that way, but I am not sure.
What did you see instead?
I got an error 404, as if the service is not configured at all, which is different from being configured and just not available.
What version of Traefik are you using?
What is your environment & configuration?
If applicable, please paste the log output in DEBUG level
No response
The text was updated successfully, but these errors were encountered: