Nomad Provider: Services are registered as healthy immediately without waiting for Nomad health status (TODO in code)

[VolkerK]

Welcome!

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

What did you expect to see?

Hello Traefik team,

we are using Traefik with the Nomad Provider and have encountered the following issue:

The Nomad Provider registers new services immediately as healthy, without waiting for Nomad to report them as healthy. There is a TODO in the code to address this behavior: TODO in config.go

We also have Traefik’s own health checks enabled, but the service only gets marked as offline after the first failed health check. Currently, we have not found a way to register a new service as offline initially until the first successful health check occurs.

Problem We want to replace/update services/servers in Traefik without any interruption, but with the Nomad Provider this seems impossible under the current behavior. Are we missing something?

Will the TODO in the Nomad Provider be addressed?

Thank you!

[kevinpollet]

Hey @VolkerK,

Thanks for your suggestion, we think it makes a lot of sense.  Unfortunately, this would not make it to our roadmap for a while as we are focused elsewhere.  If you or another community member would like to build it, let us know, and we will work with you to make sure you have all the information needed so that it can be merged.

Don’t forget to check out the contributor docs and to link the PR to this issue.