Healthchecks

[j-kinyanjui]

I have this system currently in testing and rolled out in DC/OS. When jwt verification is set as true for certain micro-services (specifically, client and user). While accessing the /health endpoint, the service responds with an Unauthorised response. Is there a fix for this? Or does this require a fix by separating the health check path from the other GET paths? I don't think a health check path should require a jwt token.
The client micro-service /health endpoints also seems to be missing/broken
curl -k https://localhost:6884/health
{"statusCode":404,"code":"ERR10007","message":"INVALID_REQUEST_PATH","description":"Request path /health cannot be found in the spec."}

[stevehu]

In light-platform, the health check endpoint is accessed from light-portal which has a token with scopes only for health check and server info. I see your point for the integration with other ecosystems. Maybe we should make it configurable so that end user can control if this endpoint is protected or not. Thanks for bringing it up.