Kishor Joshi

@ArpanShah2k, thanks for your interest, I will assign it to you. /assign @ArpanShah2k

The pod termination handling and the Endpoint/EndpointSlice update happen in parallel. Controller de-registers the targets after getting updated Endpoint from the API server. There is a similar issue reported earlier:...

@jmturwy, the controller relies on the admission wehbook to validate, as well as apply default values. We currently don't have plans to make the admission webhook optional.

@jmturwy, closing the issue since we don't plan to support disabling the webhook.

@dusansusic, would you be able to share the controller logs? You can email them to k8s-alb-controller-triage AT amazon.com

@dusansusic, With readiness gates, controller waits for the pod `ContainersReady` to be true before registering the target. If containers ready is not true, the tgb controller requeues the reconcile request....

@theintz, in case of errors, controller will not reconcile the ingress or the group further. If you use ingress group feature, fatal errors encountered during processing of one ingress affects...

@adammw, thanks for the feature request and the PR. We will sync up internally with the NLB team to see if they have plans to support ipv4pool natively.

Since you've specified the service annotation `service.beta.kubernetes.io/aws-load-balancer-type: nlb`, the NLB gets reconciled by the in-tree controller which does not support specifying ALPN policies. If you want this controller to reconcile...

@tleish, with the `service.beta.kubernetes.io/aws-load-balancer-type` annotation change, I'd recommend to delete the existing service and create a new service with the desired value. Since the state is pending, could you verify...