<p>I have few questions related to the container platforms (K8S, Openshift, etc.) and how should be the Environments (Prod, Stage, QA, Dev, etc) be separated and Issoleated in the said platform; Where I would like to share some questions that arise when you are selecting and/or identifying how many clusters do you really need and How many actually are necessary for an implementation of a Container Platform, keeping the best practices and leverage with the benefits of this kind of platforms.</p>

<p>Well, the issue of container platforms where and how to implement one with 1 or more clusters is a controversy, Where do I get the following questions?;</p>

<ul>
<li>A single Container Platform Cluster is enough, and leverage Logically isolate (namespaces)?</li>
<li>Is it okay to have separate environments (production, staging, quality control, etc.) by Cluster? that is, a Cluster by Environment?</li>
<li>When do I need more than one container platform cluster?</li>
<li>The horizontal growth of the platform should be in nodes and / or in clusters?</li>
<li>What would be the best practices for this type of platform at the Architecture level?</li>
</ul>

<p>Taking as well into account the economic aspects that can be drastically presented in the implementation of one of the platforms according to the number of Clusters to be used in case if its more then ones; equally the distribution of resources for tasks.</p>

<p>Example of a container platform with dedicated resources for each environment and used logical isolation.</p>

<p><a href="https://i.stack.imgur.com/uZJ3X.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/uZJ3X.png" alt="![clipboard.png](inkdrop://file:0D1o5piJz)"></a></p>

<p>Example of a Containers platform with resources dedicated by Cluster.</p>

<p><a href="https://i.stack.imgur.com/UC6Pf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/UC6Pf.png" alt="![clipboard.png](inkdrop://file:cZQCMbG4J)"></a></p>

<p>I understand that there are several questions in the same post, but as I mentioned, it is a controversy, other concerns will arise, and the idea is to stay attached to the best practices for the implementation of this type of solutions, just as we can leverage with the benefits that this type of platform does not provide to reduce costs and maintain a simple architecture and implementation.</p>

<p>Thanks in advance and it will be a pleasure to read your comments and opinions.</p>

Fulvio
<p>In OCP you usually not dedicate nodes to certain environment. You do that at the projects level.     </p>

<p>Create specialized dedicated worker nodes ("Infra" nodes) to run ingress controllers per environnment: a LB will route external traffic to a pair of IC per env that will process routes for projects assigned to one environment etc. So you can have a pair of nodes with ingress controller per environment and a LB in front of them etc. </p>

<p>A project will contains apps from one environment (either prod or uat or ..): better one project per app per env. You can assign a project to an egress IP address for communication outside the cluster from an egress range so you can easily configure your external firewall as it will know from what egress assigned to an env it comes from etc.    </p>

<p>Projects are isolated per default and you can even isolate them more with<code>NetworkPolicies</code>. Also you can have your nodes spread on multiple vlans etc..</p>

<p>...</p>
