You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VPC-A, subnet-A and EC2-A are provisioned
VPC-B, subnet-B and EC2-B are provisioned
TGW-A & TGW-B are provisioned and attached on both sides
I can add a 0.0.0.0/0 route (or a more specific route) to Subnet A or B that maps to a destination of TGW-A / TGW-B
I can add a 0.0.0.0/0 route (or a more specific route) to the TGW-A / TGW-B route table that points to the remote TGW
Definition of Done
There is an example in this repo that allows EC2-A to talk to EC2-B via a TGW.
done edit:
We essentially just want to add logic to our VPC module where we optionally create a TGW and attach another VPC
Question: Can I add routes for subnets with our current VPC module?
my vote would be to use this as it feels weird to use some cloud posse iac modules and not others; however, I'm not opposed to evaluating previous decisions on this and shaking up a lot of the IaC things
As a platform engineer / user of secure mode, I would like the ability to place my k8s workloads behind a separate boundary / account.
I would like the following in the VPC module or example.
This feature is needed to place the private eks loadbalancer behind a boundary in a different VPC connected via TGW.
The text was updated successfully, but these errors were encountered: