amazon-apigateway-ingress-controller icon indicating copy to clipboard operation
amazon-apigateway-ingress-controller copied to clipboard

Published 20 hours ago • verified publisher icon awslabs

Cloudformation subnet issue

Open korobass opened this issue 4 years ago • 1 comments

Hi Guys,

I have noticed that automatic subnets ids discovery is prone to errors. It is happening when you have multiple private subnets in the same availability zone.

What's is happening: APIGW ingress controller is creating a CloudFormation template that contains the list of all private subnets, in our case list contains two private subnets in each availability zone. The creation of a cloud formation stack initiated by the APIGW ingress controller is failing, due to the inability to create a network load balancer located in more than one subnet in the same availability zone.

Suggested solution: Implement additional annotation similar to ALB ingress controller to provide explicitly subnet ids: e. g. apigateway.ingress.kubernetes.io/subnets: s-id1, s-id2, s-id3

Best Regards, Marek K.

korobass avatar Aug 21 '20 11:08 korobass

+1

mkamel93 avatar Aug 31 '20 12:08 mkamel93