-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Consul 1.7 consecutive pass/fail on health checks #6913
Comments
What ... postponed again! 😭 |
Sorry about the postponement @shantanugadgil , this is blocked by |
Looks like hashicorp/consul#7949 got merged for Consul v1.8.1, however we still need an updated |
Upgrade our consul/api import to the equivelent of consul@v1.8.1 which includes a bug fix necessary for #6913. If consul would publish a proper api/ submodule tag we could reference that.
Upgrade our consul/api import to the equivelent of consul@v1.8.1 which includes a bug fix necessary for #6913. If consul would publish a proper api/ submodule tag we could reference that.
This change adds the ability to set the fields `success_before_passing` and `failures_before_critical` on Consul service check definitions. This is a feature added to Consul v1.7.0 and later. https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical Nomad doesn't do much besides pass the fields through to Consul. Fixes #6913
🎉 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Consul 1.7 provides support for configuring health checks to become passing/critical only if a specified number of consecutive checks return passing/critical. Nomad service health check config should also allow this configuration.
The text was updated successfully, but these errors were encountered: