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 readiness endpoints to all services #116

Open
jbygdell opened this issue Mar 13, 2019 · 2 comments
Open

Add readiness endpoints to all services #116

jbygdell opened this issue Mar 13, 2019 · 2 comments

Comments

@jbygdell
Copy link
Collaborator

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 a 200 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.

@anandmohan777
Copy link
Collaborator

@jbygdell We are using TCP liveness probe in all the services, we use the same for readiness probe?

@jbygdell
Copy link
Collaborator Author

jbygdell commented Mar 13, 2019

I use the liveness probes as well, but they report ok before the service is ready to accept external connections.

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

No branches or pull requests

2 participants