Connectivity through AWS Transit Gateway

[RamazanKara]

In our Organization we have a huge amount of Teams with lots of EKS Clusters distributed throughout the Organization, making the usage of VPC Peering compared to Transit Gateway a lot more complicated. Will there be upcoming support of Transit Gateway usage for the MCS Controller?

[runakash]

Hey @RamazanKara - The MCS controller does not have explicit VPC Peering support. In fact, the controller itself is agnostic of how the network connectivity is going to be established between services across the clusters. It takes care of the Service Discovery only. That said, we have only tried out VPC Peering. Why don't you try it out with Transit Gateway and let us know of any issues. We can probably address those in future milestones.

[RamazanKara]

Thanks for the info. I will gladly test out the connection through transit gateway and report back how it worked for me so far.

[vvbogdanov87]

Does the MCS controller work only when pods in both clusters are in routable networks? Eg workers in both clusters are in routable subnets with non-overlapping address spaces. For pods, I configured a secondary non-routable subnet with overlapping address spaces. When I create a service, it creates an ALB in a routable subnet. Will MCS register pods by IPs or by ALB IP?

[runakash]

Does the MCS controller work only when pods in both clusters are in routable networks?

The clusters need to be in the peered networks. And for peering to work the clusters does need non-overlapping address spaces.

Will MCS register pods by IPs or by ALB IP?

Register pods by IPs.

This blog post will be helpful to understand the functionality better.