Skip to content

Commit 26b29d7

Browse files
Merge pull request #218254 from khdownie/kendownie-aks-28820
adding container size considerations
2 parents e8d1a6a + 1a3fbc6 commit 26b29d7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/aks/quotas-skus-regions.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,12 @@ Each node in an AKS cluster contains a fixed amount of compute resources such as
3838

3939
For more information on VM types and their compute resources, see [Sizes for virtual machines in Azure][vm-skus].
4040

41+
## Supported container image sizes
42+
43+
AKS doesn't set a limit on the container image size. However, it's important to understand that the larger the container image, the higher the memory demand. This could potentially exceed resource limits or the overall available memory of worker nodes. By default, memory for VM size Standard_DS2_v2 for an AKS cluster is set to 7 GiB.
44+
45+
When a container image is very large (1 TiB or more), kubelet might not be able to pull it from your container registry to a node due to lack of disk space.
46+
4147
## Region availability
4248

4349
For the latest list of where you can deploy and run clusters, see [AKS region availability][region-availability].

0 commit comments

Comments
 (0)