AKS Virtual Nodes - Resources - Limits vs Requests

[jonstelly]

Trying to launch a pod on an AKS Virtual Node, there appears to be a need to match limits to requests: virtual-kubelet/azure-aci#17

That requirement is not at all intuitive and can be very difficult to do if using sidecars like a service mesh, etc...

If Limits of all containers in a pod > Requests of all containers in a pod, the ACI Connector gives the following error:

time="2021-07-07T20:33:17Z" level=error msg="failed to create container group default-my-worker-00007-deployment-68f476fd9b-phjzn" azure.region=... azure.resourceGroup=me-dev-...-kube error="api call to https://management.azure.com/subscriptions/...: got HTTP response status code 400 error code "ContainerLimitGreaterThanContainerGroupTotalRequest": The 'Cpu' limit '1.5' in container 'me' is greater than the total request '0.3' of container group 'default-my-worker-00007-deployment-68f476fd9b-phjzn'." key=default/my-worker-00007-deployment-68f476fd9b-phjzn method=aci.createContainerGroup name=my-worker-00007-deployment-68f476fd9b-phjzn namespace=default node=virtual-node-aci-linux operatingSystem=Linux phase=Pending pod=my-worker-00007-deployment-68f476fd9b-phjzn provider=azure reason=ProviderFailed uid=e2ddabce-1032-4768-80ac-110720d38c8f watchedNamespace= workerId=12

I haven't yet deciphered the exact rules, but it should definitely be figured out and included in the documentation.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b423e65f-2562-5711-bff0-c4ac3371161c
• Version Independent ID: cf6cd7ae-6849-64da-d6a9-effb6f2fe86a
• Content: Use virtual nodes - Azure Kubernetes Service
• Content Source: articles/aks/virtual-nodes.md
• Service: container-service
• GitHub Login: @mlearned
• Microsoft Alias: mlearned

[Karishma-Tiwari-MSFT]

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

[zr-msft]

Thank you for the feedback.

We have added an item to our backlog and will prioritize accordingly.

#please-close

[schaffererin]

#reassign:schaffererin
#please-open

[schaffererin]

Hi, @jonstelly, thank you for your feedback and for your patience. I apologize for the delay in responding. I've reached out to the proper product and engineering teams. They've informed me that this is not a docs-specific issue. The README has been updated with the supported features/limitations. I will close this issue now. Thank you again!

#please-close