Kishor Joshi

@przemolb, you can add multiple ports to the service spec which will translate to multiple listeners on the NLB.

You could use the targetgorupbinding. If you use tgb, you 'd need to create the NLB and its target groups manually. You can use targetgroupbinding to associate a NodePort (for...

The NLB target registration can take from 90 to 180 seconds to complete. After registration, the targets are marked healthy only after the configured health check passes. This delay is...

@youwalther65, ALB IP target registration is faster than NLB.

@michaelkoro, we can optimize in limited situations - for consecutive rules so as to honor the ingress group order. Also the current ALB limit is max 5 conditions per rule....

@wildtapir, you could describe the load balancer based on the name which you can get from the ingress status field. Once you have the load balancer ARN, you get the...

Here is one way to do it - From the kubectl output, look for the status field, you will see the load balancer DNS name - Extract the load balancer...

This controller applies labels to all k8s resources it creates, for example all TargetGroupBinding resources created by this controller have the following labels: * explicit IngressGroup * `ingress.k8s.aws/stack: groupName` *...

/kind feature Currently, the default target type for Ingress and Service with loadBalancerClass is `instance`. The load balancer class is supported in k8s 1.22 and later versions. For legacy service,...

The current KCM or CCM doesn't modify the load balancer tags for NLB on service edits, NLB tags are configured during service creation only. CLB tags should work as expected....