Skip to content

Ingress subnet auto-discovery for subnets in different account linked via Transit Gateway

0

We have a Networking account in which I have configured public subnets that are connected via the Transit Gateway to the subnets of the testing environment account. In the testing environment, I have an EKS cluster on which I need to deploy an ingress capable of auto-discovering the public subnets. However, the ingress always returns the following error (despite having correctly configured the Transit Gateway routes and the tags of the public subnets in the Networking account): Failed build model due to couldn’t auto-discover subnets: unable to resolve at least one subnet (0 match VPC and tags: [kubernetes.io/role/elb])

How can I resolve this?

1 Answer
0

Maybe you could use VPC sharing to share subnets with other AWS accounts within the same AWS Organization, like this: https://aws.amazon.com/cn/blogs/containers/expose-amazon-eks-pods-through-cross-account-load-balancer/

AWS
SUPPORT ENGINEER
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.