Cloud HTTP health check of LoadBalancer keep UNHEALTHY

[danielcaro]

Problem:

When the service is deployed to GKE or any K8s behind load balancer with health check, the validator will try fetch HTTP response or TCP (https://cloud.google.com/load-balancing/docs/health-check-concepts#criteria-protocol-ssl-tcp) , but the Java Websocket implementations make fail the health check, and the service keep UNHEALTHY .

Solution:

Implement a Draft_HttpHealthCheck using the suggestion proposed by @SerVB at TooTallNate/Java-WebSocket#1077 becauseJava_Websocket owner said that will not provide a draft to support http health check.

PS:
If you like I can send a PR with my approach solution, that already works well :D .

[TVolden]

Hi @danielcaro

Yes please set up a PR, I'll gladly review your code and merge it if it passes the automated tests.

Sincerely,
Thomas

[danielcaro]

Hi, I found some problems now, I gonna test the solution at production first. Then I'll sent the PR.

[danielcaro]

The solution was tested on production, but I would like to hear your advice.

#189

[TVolden]

Okay, the PR is merged. Please check if it works as intended and close the issue :)

[fabiangr]

Hi @TVolden , hi @danielcaro ,

I would like to use your library within a Spring Boot Project and use Spring's implementation for health checks etc (Actuator). As far as I understand it, the current implementation answers 200 OK on every possible HTTP route I could call. Is there a way to deactivate this behaviour or limit it to certain routes to be able to use my own implementation?