Skip to content
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 Marathon readiness checks #1559

Closed
timoreimann opened this issue May 5, 2017 · 1 comment
Closed

Support Marathon readiness checks #1559

timoreimann opened this issue May 5, 2017 · 1 comment
Assignees
Labels
Milestone

Comments

@timoreimann
Copy link
Contributor

timoreimann commented May 5, 2017

Readiness checks are a means to prevent Marathon tasks from being taken into LB rotation prior to them being ready to serve traffic. The idea is that applications define a readiness check HTTP endpoint along with a number of parameters in the Marathon specification, which will cause Marathon to only mark a task as ready during the deployment of the associated application if that endpoint returns a successful response.

Traefik already vendors a copy of the go-marathon that brings readiness check support. The only thing left to do in Traefik is to filter out tasks whose readiness check result is not positive.

Refs #1185.

@timoreimann
Copy link
Contributor Author

Internally, I have already implemented the necessary logic for Bamboo. It should be fairly trivial to port it to Traefik, which I'm going to do.

@timoreimann timoreimann self-assigned this May 5, 2017
@ldez ldez added the priority/P2 need to be fixed in the future label Jun 13, 2017
@traefiker traefiker added this to the 1.4 milestone Aug 18, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants