Support for newer versions of Consul
yacinelazaar opened this issue · 10 comments
Howdy,
Was wondering if there are any plans to support later versions of Consul for this project?
Thanks.
How much later? Is there a particular feature that does not work?
Hey, thanks for reaching back.
Would like to use Consul's service mesh (Consul Connect) but couldn't make the registrator work with official Consul images and had to rely on gliderlas's server and agent images to make service discovery work. Perhaps I misconfigured something but I had to be sure. Is it the only way the registrator is meant to work?
Interesting, I don't use Consul Connect (yet), but I want to start soon.
Well, Is the registrator coupled to gilderlabs server/agent images?
It is not. What part of the docs say that it would be?
Allow me to chirp in here. Also properties for health checks like:
failures_before_criticalinterval
are not supported as far as I can see. Would be great to have as well. And can anyone tell me the syntax for registering a health check in newer version of Consul 1.7.0+ .... where it is a script check. Like described here: https://gliderlabs.github.io/registrator/latest/user/backends/ under Consul Script Check. I can't get it to work.
Thank you
We use curl as our basic health checks in containerpilot, and it works fine
That'd be your alternative to registrator
@larssb
I managed to get the registrator to work with Consul 1.7. My first trial failed and every example out there uses images managed by gliderlabs so I assumed that was the way to go.
Nice stuff @yacinelazaar .... but I will still miss the opportunity to set e.g. the Consul health check properties I mention.