I'm looking to expand our service deployment into more AWS regions for a better user experience. However, deploying EKS in every region is quite costly. I'm curious about the possibility of setting up a Kubernetes control plane in one region to manage EC2 instances across multiple regions. Additionally, I'd like to know if the EKS hybrid nodes feature shows the technical feasibility of this approach.
4 Answers
EKS can be pricey, especially if you're setting it up in each region. But consider if you really need EC2s everywhere. EKS management fees are usually a lot lower than EC2 costs. It's worth analyzing your usage before deciding on a setup.
I've been using AWS Lightsail VMs to run K8s/K3s, which saves money. I haven't got a multi-region cluster running, but I attempted something complex using Tailscale for that. I found a resource that might help, check it out if you're interested!
Absolutely, managing multiple clusters is doable, but you’ll need to think about federation, networking, and service discovery. For example, you can use Istio for networking and discovery among clusters, along with Rancher for fleet management. It's a clean and efficient setup.
Technically, yes, but it's not the best move. Using one control plane means you'll face higher egress costs, more latency, and if the region with the control plane goes down, you'll impact all other regions too. It's smarter to deploy a control plane in each region, and consider using load balancers with DNS weighting or something like CloudFront to manage traffic more effectively.
That makes sense! How much latency can I expect between the control and data planes before it becomes an issue?