I'm gearing up to establish a single Kubernetes cluster within a setup that includes three distinct network zones: an office network, a staging network, and a production network. The intended configuration comprises three control plane nodes, three etcd nodes, and additional worker nodes. I'm curious about the best approaches for architecting and configuring this cluster, especially concerning any best practices or potential pitfalls of deploying it across these isolated networks. Any advice or experiences you can share would be greatly appreciated!
2 Answers
Have you thought about using vCluster from Loft Labs? It's designed for multi-tenancy on Kubernetes and can really simplify management, especially for setups that span large scales. You might find it suits your needs! Check it out at their website.
Honestly, I would recommend setting up three separate Kubernetes clusters, one for each environment. Trying to combine all three into one cluster could lead to a lot of headaches and management issues. It just complicates things more than necessary. If you're short on resources for full clusters in each network, perhaps consider using node labels to differentiate workloads instead, but be cautious of the trade-offs!
Thanks for the input! It makes a lot of sense going for separate clusters. I'm just worried about resource limitations on-prem, but I’ll explore using node labels as a fallback.
Thanks for the suggestion! I’ll definitely look into vCluster.