<p>I am trying to size my AKS clusters. What I understood and followed is the number of micro services and their replication copies would be primary parameters. Also the resource usage by each micro services and prediction of that usage increase during coming years also needs to be considered. But all these information seems totally scattered to reach a number for AKS sizing. Sizing I meant by how many nodes to be assigned? what could be the configuration of nodes, how many pods to be considered, how many IP numbers to be reserved based on number of pods etc..</p>

<blockquote>
  <p>Is there any standard matrix here or practical way of calculation to
  compute AKS cluster sizing, based on any ones'experience?</p>
</blockquote>

Jaish Mathews
<p>no, pretty sure there is none (and how it could be)? just take your pod cpu\memory usage and sum that up, you'll get an expectation of the resources needed to run your stuff, add k8s services on top of that.</p>

<p>also, like Peter mentions in his comment, you can always scale your cluster, so such planning seems a bit unreasonable.</p>
