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
Using the container port for readiness check doesn't work for dataedge and res due to authentication requirements.
Add an non password protected endpoint to all services, /check or similar, that will return a 200 once the app is fully started.
/check
200
A non protected endpoint exists that will return a 200 when the app is fully started.
The text was updated successfully, but these errors were encountered:
@jbygdell We are using TCP liveness probe in all the services, we use the same for readiness probe?
Sorry, something went wrong.
I use the liveness probes as well, but they report ok before the service is ready to accept external connections.
No branches or pull requests
Description
Using the container port for readiness check doesn't work for dataedge and res due to authentication requirements.
Proposed solution
Add an non password protected endpoint to all services,
/check
or similar, that will return a200
once the app is fully started.Definition of Done
A non protected endpoint exists that will return a 200 when the app is fully started.
The text was updated successfully, but these errors were encountered: