<p>We are planning to deploy 15 different applications in azure kubernetes. These applications are owned by multiple business portfolios - eg: marketing, finance, legal.</p>
<p>Currently we have provisioned an AKS cluster with the following configuration</p>
<ol>
<li>Subnet : x.x.x.x/21, that gives us ~2k IPs.</li>
<li>Network : Azure CNI</li>
<li>Network policy : calico</li>
<li>Min &amp; Max nodes: Azure auto scaling</li>
<li>Min &amp; Max Pods : Based on the CPU &amp; Memory utilization, maximum allowed.</li>
<li>Azure services (eg: SQL) : Leverages service endpoints</li>
<li>On premises : Leverages private endpoint &amp; private DNS.</li>
<li>Region : West US</li>
</ol>
<p><strong>Question :</strong>
Can we deploy all the applications on the same AKS cluster? If not, what is the industry standard &amp; why?</p>

One Developer
<p>The simple answer is yes. I wouldn't call it industry standard, because AFAIK there isn't one.</p>
<p>The more complicated answer is: It depends. It depends entirely on the security requirements you need to adhere to for the applications you're deploying.</p>
<p>There's a number of ways you can manage this in a single cluster, assuming you want to prevent access (Network / User) via RBAC and the CNI within Kubernetes. It does make things more complicated but arguably less cumbersome long term.</p>
<p>You could separate out the different apps through namespacing, node taints. There's a lot of different options that will be dependent on the requirements you need to fulfill for your clients / company.</p>
<p>Even if you have region specific requirements, you can manage this in a single environment.</p>
