Kishor Joshi

@johurul000, sure, that would be wonderful. I will assign the issue to you. Feel free to reach out if you need further help. /assign @johurul000

@johurul000, you can use any k8s on AWS.

@minusv, @wwteo, could you share the full manifest of the service? Did you ensure the NLB got provisioned by this controller? If the LB name starts with `k8s-`, then it...

IngressClass is for ALB. For NLB, you will have to provision a service resource of type LoadBalancer, and the following annotations: ``` service.beta.kubernetes.io/aws-load-balancer-type: external service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: instance ``` or ``` service.beta.kubernetes.io/aws-load-balancer-type:...

@wwteo, I'm closing the issue since it is possible to attach multiple SSL certificates to the NLB provisioned by this controller. if you still face issues, feel free to reach...

@guillaumecle, how do you intend to configure the target group names? The target groups are based on the backend service, and it can be shared across multiple ingresses. The target...

@guillaumecle, we use tags to identify target groups/load balancer resources, so the name doesn't matter to the controller. However, controller needs to ensure the name is unique. We can support...

@wuyudian1, this is not something we can support at the moment. It requires at least the following features: - Controller support multiple VPCs - possibly run multiple controller instances in...

@kncesarini, I see you specified the healthcheck port/protocol/path manually and is different from the traffic port, it should have worked. I'm not familiar with kong-ingress proxy. Would you be able...

@kncesarini, since we've not heard back for a while, I'm closing the issue. If you have further concerns, feel free to reach out to us.