traefik: v1.2.0-rc2 traefik does not respond to kubernetes ingress create/delete events
What version of Traefik are you using (traefik version)?
v1.2.0-rc2
What is your environment & configuration (arguments, toml…)?
kubernetes 1.5,2
- args:
- --web
- --kubernetes
- --logLevel=DEBUG
- --web.metrics.prometheus
- --web.metrics.prometheus.buckets=0.1,0.3,1.2,5
I have traefik exposed through an ELB which has a DNS entry *.mydomain.com pointed at it.
I have a bunch of ingresses configured at <svcname>.mydomain.com.
What did you do?
I created an new ingress for a service at host mysvc.mydomain.com
and expected to be able to find the service there, but instead I got ‘Bad Gateway’
What did you expect to see?
The HTML returned by my service
What did you see instead?
Bad Gateway
What did you do?
I then deleted an ingress for a different service with an ingress at myothersvc.mydomain.com, which I had verified was working.
What did you expect to see?
Bad Gateway or something indicating that there wasn’t a provider for this URL
What did you see instead?
The HTML returned by the service.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 23 (4 by maintainers)
I’m not sure its entirely working correctly I still a very high number of 404’s being returned in the health screen. Not the same ratio as before, however. I am trying to track down the source of those.I’ll keep it running in dev and see if the devs complain.
@rrichardson I just pushed the docker image
containous/traefik:c582ea5ff0c72df13962eeca4bff3b337db4e865that contains the latest fix. It would be awesome if you could confirm that it now works 😃