Hi
I was trying to Generate AWS ALB through All-in-one-kong-deployment.yaml, but its not working, can anyone help me regarding this?
Snippet where i suppose to tell ALB created i.e at KONG-PROXY-SERVICE k8 object as follows:
Please elaborate on what is not working. Is the LoadBalancer not being provisioned or are you having trouble in forwarding traffic from the LoadBalancer to Kong?
I am able to create Classic Loadbalancer and Network Loadbalancer as well. But when I opt for Application Load Balancer, it creates CLB only not a ALB on AWS account. service.beta.kubernetes.io/aws-load-balancer-type: “alb”
I guess in above line , We mention whether we have to create CLB or NLB or ALB. Help me with this.
We have been using the alb-ingress-controller and been pointing to kong-proxy backend for a long while with no issues at all. As Satwant mention, this seems to be the only solution that is currently available.
I’m also stuck here. You can’t really us an Application Load Balancer. Note that in the context of K8s alb can be either Amazon Load Balancer or Application Load Balancer.
My issue is that I can forward the TLS terminated connection to Kong but Kong assumes it is on the edge of the network and that the plain connection is not encrypted and erroneously flagged as http and not https.
I have read that King doesn’t support proxy protocol v2. Is that true?
If it doesn’t then how are we supposed to use it with an NLB?
Hey all,
We are stuck in the same step. Tried to use alb-ingress-controller on top of the Kong ingress controller with alb path routing. But it does not resolve some of the Kong static content, most probably due to path-based routing.
Can someone please shed some light on this matter?
CristianPupazan, ltartarin90: It would be really great if you can share any references if you have any, so we can go through it.
Hi @Chamin_Wickramarathn@CristianPupazan Could you guys please guide how I can point kong ingress controller to use alb or share some reference links which would be helpful
Thanks
I kinda have the same set-up as Cristian. I deployed ALB + EKS with terraform, the only catch is i need to predefined the NodePort port number in the automation , and ensure the port number is match and specify in the Kong Helm chart values.
Hi Cristian, with this approach you’ve attached - and we have exactly the same in our infra - were you able to use Kong’s CRDs for the infrastructure configuration? I know they provide decK solution, I just wanted to use K8S specs do define the whole routing etc. I was able to define all necessary plugins with IaC approach, unfortunately, since routes are defined in kong via Ingress, did you manage to define them with your setup?
Hi Jan,
We are not using the ingress for this setup (we use the ingress controller somewhere else for internal endpoints but without the ALB). We had this setup running for a long time, I believe before the ingress controller got released, and haven’t got around to changing it yet. We use helm to deploy our services and each service has a helm hook where it registers its routes, and plugins interacting with the kong admin directly.
I recently worked on a new implementation using OAuth2.0 plugin and migrate from NLB to ALB to make use of WAF policies. Starts returning http problem.
After some digging, we found out that the issue was the backend-protocol on the Target Group was set to HTTP by default, so we add this annotation to the Ingress for Kong:
hi @CristianPupazan
I also deployed ALB + kong ingress + EKS like you. But I still have problem the nodeport healthcheck. currently, i reach the healthcheck error 404 in target group
can i know how are your configure ?