Kishor Joshi
Kishor Joshi
@machad, controller maintains rule order for `ImplementationSpecific` path types only. `Prefix` and `Exact` path types need to honor the precedence defined in the ingress spec - https://kubernetes.io/docs/concepts/services-networking/ingress/#multiple-matches
@pmichna, are these IPs 172.16.128.63 and 172.16.116.101 are assigned to your api servers? The webhook ports require TLS 1.3 and are for access only by the api servers.
@gals-ma, the two replicas are in active-standby mode. The issue is not with the controller itself, but the API server is not responding to the controller request. It could either...
@owyah, I'm closing the issue since recent releases have a separate manifest for IngressClassParams.
@justinrlee, controller provisions internal NLB by default unless you specify the scheme via the annotation `service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing`. Since you've specified the loadBalancerClass, the annotation `service.beta.kubernetes.io/aws-load-balancer-type: external` has no effect.
@agconti, @timharsch could you check whether your security groups have the following tags? ``` ingress.k8s.aws/resource: ManagedLBSecurityGroup elbv2.k8s.aws/cluster: ingress.k8s.aws/stack: ``` If these tags are not present on the security groups, then...
@agconti, the aws cli is to update existing SG ingress on your EC2 SG added by the v1 controller. If the permissions list is empty, either the sg is not...
@LechG, thanks for your contribution. We will relax the single cert per host restriction in the v2.5.0 release, PR #3028 will address this. Closing this PR in favor of 3028.