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

Add "/ready" endpoint to health check #14089

Closed
leszko opened this issue Nov 8, 2018 · 1 comment · Fixed by #14152
Closed

Add "/ready" endpoint to health check #14089

leszko opened this issue Nov 8, 2018 · 1 comment · Fixed by #14152

Comments

@leszko
Copy link

@leszko leszko commented Nov 8, 2018

The /ready endpoint should return HTTP_OK if a member already joined (or formed) a cluster. So, the user can safely use that member. It would be helpful in the following scenarios:

  • in Kubernetes service: not to send any traffic to unready member
  • in Kubernetes Rolling Upgrade - to restart member and wait until it joins to cluster, before the next member is terminated

Such an approach will improve K8 user experience and will guarantee that the cluster will not reduce its size significantly during rolling upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants