Kishor Joshi

@ttony, the controller currently assumes exclusive ownership for the target groups. Target groups should not be shared across multiple controllers to avoid any race condition.

/kind feature Here is the outline - maintain a configmap for each tgb - add all targets to be registered to the configmap - when deleting targets, limit to the...

@sn-asownie, could you provide the following? - Ingress or service (ALB or NLB) - if ingress, did you configure security groups manually via annotation? - Controller logs

@sn-asownie, > One question I had is if having two separate clusters with their own ALB in the same account is supported. We support this configuration. From the logs we...

@sn-asownie, I'm closing the issue. If problem persists, feel free to reach out to us.

/kind feature

@micemuni, in your case, you'd specify the logging configuration via the `alb.ingress.kubernetes.io/load-balancer-attributes annotation`. For further details, please refer to the live doc https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#load-balancer-attributes

@micemuni, I'm closing this issue. If issue persists, feel free to reach out to us.

@niall-d-tw, did you intend to create a single load balancer for both VPCs or looking for multiple loadbalancers on each of the VPCs? could you clarify further?

@niall-d-tw, we don't have plans to support one ingress mapping to multiple load balancers at the moment.