KONG on EKS with ALB

[Prateek_Khandelwal]

I want to use kong with ALB for stable GRPC connections, so I changed the service type of Kong Proxy from LoadBalancer to NodePort, and created a custom ingress in the same namespace, ‘/’ route is forwarded to service name of kong proxy and nodeport.
but the health checks for the ALB are failing.
Can you help me out with this.

I followed this thread, it works for rest connections (HTTP/HTTPS) but not for GRPC

Kong with AWS Application Load Balancer

hi, sorry for the late reply. 1. deploy the alb-ingress-controller Instructions to install the alb-ingress-controller can be found here (I used helm ): https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html 2. deploy the kong-proxy Deploy kong without creating a load balancer (use NodePort type). I used helm again: https://github.com/Kong/charts 3. Create your ingress Then create your ingress pointing to the kong proxy service: apiVersion: networking.k8s.io/v1…

[Plenue]

Facing similar issue. Seems like ALB have some issue with GRPC.

[harsh.kumar]

Have been trying to do a similar thing, setting the proxy service as a NodePort to use ALB for GRPC.
Facing a similar issue.