<p>I'm new in the Kubernetes universe and I have some doubts about an implementation that I want to do.</p>
<p>I have the following scenario: I have 200 instances of a worker that executes some business logic and the unique thing that differentiate them is the input parameters.</p>
<p>I was thinking in to use AKS to scale up this infrastructure according to the input parameter and dynamically, only create a new pod when exists the demand for the worker with the input parameter &quot;XYZ&quot;.</p>
<p>Simple architecture draft:</p>
<p><a href="https://i.stack.imgur.com/cDVii.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/cDVii.png" alt="enter image description here" /></a></p>
<p>I have an API that receives a request and with base in this request, an orchestrator send the request for the correct worker.</p>
<p>So I'd like to know if this type of architecture is possible with AKS and if is a good approach.</p>

<p>This is one of the scenario where you can use Azure Functions with <a href="https://azure.microsoft.com/en-gb/solutions/architecture/scale-using-aks-with-aci/" rel="nofollow noreferrer"><code>ACI</code></a> or with <a href="https://keda.sh/" rel="nofollow noreferrer"><code>KEDA</code></a> to autoscore the containers based on the demand.</p>
<blockquote>
<p>Use the AKS virtual node to provision pods inside Azure Container
Instances that start in seconds. This enables AKS to run with just
enough capacity for your average workload. As you run out of capacity
in your AKS cluster, scale out additional pods in Azure Container
Instances without additional servers to manage.</p>
</blockquote>
<p>Here is my blog on <a href="https://sajeetharan.com/2020/09/26/scale-your-applications-with-kuberenetes-based-event-driven-autoscaling/" rel="nofollow noreferrer"><strong>Scale Applications with Kuberenetes-based Event Driven AutoScaling</strong></a></p>
