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.

Sign up for GitHub

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

Jump to bottom

make the health check path configurable in the portal-registry #932

Closed
stevehu opened this issue Apr 20, 2021 · 1 comment
Closed

make the health check path configurable in the portal-registry #932

stevehu opened this issue Apr 20, 2021 · 1 comment

Comments

@stevehu
Copy link
Contributor

stevehu commented Apr 20, 2021

For users that deploy services to a Kubernetes cluster, it usually has two probe endpoints to differentiate liveness or readiness. This change will give users the flexibility to use /health/ or /health/readiness plus the serviceId for the health check from the light-controller or light-poral.
stevehu added a commit that referenced this issue Apr 20, 2021
@stevehu
fixes #932 make the health check path configurable in the portal-regi…
afe274f 
…stry
@stevehu
Copy link
Contributor Author

stevehu commented Apr 20, 2021

make the health check path configurable in the portal-registry light-4j master

younggwon1 pushed a commit to younggwon1/light-4j that referenced this issue Feb 10, 2024
@stevehu
fixes networknt#932 make the health check path configurable in the po…
256f0b9 
…rtal-registry (networknt#933)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stevehu