You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 27, 2020. It is now read-only.
Problem is HTTP Load Balancer setup default health check rule which expects HTTP 200 status to the GET requests on / path. Kong doesn't provide that out of the box. Does Kong provide any other health check endpoint that I can use with GKE Ingress?
The text was updated successfully, but these errors were encountered:
I had the same problem. The only thing I found that I thought would work for me is the suggestion in this thread but I have not gone this route yet as I am not familiar with configuring Kong and do not have time to learn at the moment. I ended up going a more manual route of just configuring a LoadBalancer service on Kong and scripting the DNS set up. Not ideal but it works for now. It would be very helpful if there were standard readiness and liveness endpoints on the public port that do not require authentication (although I am sure there are all sorts of reasons this is not as straight forwards as it sounds).
@kevinhcross I configured a LoadBalancer service on Kong, And use konga to enter Kong for configuration management; When I'm done configuring on / path, I'm reusing the Ingress rule.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
##How do I deploy Kong with HTTP Load Balancer on GKE
I am trying to setup Kong on GKE with HTTP Load Balancing. GKE allow creation of HTTP Load Balancer with Ingress Resource. It's documented here.
https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer
Problem is HTTP Load Balancer setup default health check rule which expects HTTP 200 status to the GET requests on / path. Kong doesn't provide that out of the box. Does Kong provide any other health check endpoint that I can use with GKE Ingress?
The text was updated successfully, but these errors were encountered: