Kishor Joshi

@prajithp13, you can follow the upgrade guide from https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/deploy/upgrade/migrate_v1_v2/. You can use the latest v2.4.1 You will need to ensure the iam permissions for the controller contains all permissions mentioned...

@rampn443, could you check if the comments from a prior issue https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1090#issuecomment-561842212 helps? If not, would you be able to share the ingress spec?

@rampn443, closing the issue since we did not hear back from you. For websocket, you need to ensure: - your ingress has rule for the initial request path to the...

@tanvp112, in case of internal NLB with IP targets, the controller adds SG rules for each of of the load balancer subnets CIDRs. Since the target is healthy, the appropriate...

If cross-zone load balancing is disabled, the DNS records corresponding to the AZs without any targets get removed from the NLB. Could you verify whether cross zone load balancing is...

@vipulJain05, ALB currently doesn't support HTTP 308 redirect. For the redirection, you can provision a NLB with your your application issuing the required redirect - this is a bit costly...

Controller will not be able to support this unless it is available on the ALB side. We are tracking this request in issue 1571.

@thanhma, do you use auto-discovery? If so, does the controller resume once you import new certificate for the domain under question?

@amarkezic, could you check the chart version you applied? ensure you run `helm repo update`. To check the chart version `helm show chart eks/aws-load-balancer-controller` The chart version should be 1.4.1

@hintofbasil, Are you looking for both the controllers to modify the same target group? Assuming your clusters are on the same VPC, if you have different target groups, then you...