Add route to HealthCheck (useful in deployments to GKE) #416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this PR is to provide a route for checking the life of the service.
This is extremely useful when the service is being deployed to GKE using GCE Ingress control.
This was an open discussion and seen as a limitation in the service's helm graph, as can be seen here: codecentric/helm-charts#627
Basically, when the service is configured with basic authentication, there is no route that returns Http code
2xx
, so the Ingress-GCE life check cannot validate that the HTTP port exposed by the service (8025
) is working correctly. .Signed-off-by: Julliano Goncalves [email protected]