Kishor Joshi

/assign @M00nF1sh Investigate further on the periodic sync issue This is similar to https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2515

@owyah, did you install the controller via manifests instead of helm chart? If so, can you verify you have the ingress class named alb in your cluster? You can apply...

In v2.4.3 patch release, we separated the IngressClass and IngressClassParams from the full manifest due to race condition with the kubectl apply - issue #2672. Starting recent v2.4.4 patch release,...

@Yagyansh, the DDoS mitigation is a new feature, the controller doesn't support configuring it yet as of v2.4.3 release. We will add the feature in future. In the meantime, you...

It is possible to create ALB in one account and the target-group targets in another account, but you will need to configure the following: - vpc peering - route table...

@rastislavs, we already support dual-stack NLB/ IPv6 clusters via the external AWS Load Balancer controller - https://github.com/kubernetes-sigs/aws-load-balancer-controller/. Is there any reason you are unable to use the external controller?

The auto-discovery excludes subnets not tagged for the current cluster but contains the`kubernetes.io/cluster/{clusterId}` tags for some other clusters. The role tag alone does not impact the auto-discovery, it helps determining...

/triage accepted

k8s 1.20 and later support the service annotation `service.beta.kubernetes.io/aws-load-balancer-healthcheck-port` to create custom health check port. I recommend using the annotation instead of this fix.

Image posted to public ECR. For details, please refer to the URL https://gallery.ecr.aws/eks/aws-load-balancer-controller.