Can I Use One EKS Control Plane for Multiple Environments?

Running both dev and prod in the same cluster can be risky. It's doable if you're just managing different services, but for environments like dev and prod, rely on namespaces to keep things organized. Just keep in mind that relying on logical separation can lead to serious issues, like data breaches or configuration mishaps that might disrupt your entire setup. It's generally more prudent to keep these environments separate, even if it means higher costs.

There’s an option with EKS called hybrid clusters, which might help, but it can complicate things further, especially when it comes to managing cross-AZ network charges. If a single interface for management is your goal, Rancher could be a good tool instead. Just a heads up, though—EKS hybrid setups are typically better suited for on-prem integration.

I remember hearing about virtual clusters at a tech talk, which could allow for this kind of setup. It sounds a bit complex, though, and I haven’t tried it yet. There's a site called vcluster.com that might be worth checking out for more info!

I hear you! It makes sense to keep dev and prod apart. However, if you're tight on budget, running your dev and QA/staging environments in one EKS cluster while keeping prod separate could save some costs. Just be careful with how you manage resources!