We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to https://freecontent.manning.com/handling-client-requests-properly-with-kubernetes/ it is not necessary to send 500 on shutdown. I think it should be avoided to have more meaning full event logs of the pods. Otherwise each shutdown generates logs of failed readiness requests
The text was updated successfully, but these errors were encountered:
a430348
🎉 This issue has been resolved in version 4.2.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
docs: add a delay before stop handling incoming requests (#12)
a0f74af
Added a note to the README.md referencing the article.
No branches or pull requests
According to https://freecontent.manning.com/handling-client-requests-properly-with-kubernetes/ it is not necessary to send 500 on shutdown. I think it should be avoided to have more meaning full event logs of the pods. Otherwise each shutdown generates logs of failed readiness requests
The text was updated successfully, but these errors were encountered: