Designing our platform architecture
In previous chapters, all of our work centered around a single cluster. This made the labs easier, but the reality of the world in IT doesn’t work that way. You want to separate out your development and production clusters at a minimum, not only so you can isolate the workloads, but so that you can test your operations processes outside of production. You may need to isolate clusters for other risk- and policy-based reasons as well. For instance, if your enterprise spans multiple nations, you may need to respect each nation’s data sovereignty laws and run workloads on infrastructure in that nation. If you are in a regulated industry that requires different levels of security for different kinds of data, you may need to separate your clusters. For this, and many reasons, these two chapters will move beyond a single cluster into a multiple cluster design.
To keep things simple, we’re going to assume we can have one cluster...
