Node-specific Volume Limits

    Cloud providers like Google, Amazon, and Microsoft typically have a limit on how many volumes can be attached to a Node. It is important for Kubernetes to respect those limits. Otherwise, Pods scheduled on a Node could get stuck waiting for volumes to attach.

    The Kubernetes scheduler has default limits on the number of volumes that can be attached to a Node:

    You can change these limits by setting the value of the environment variable, and then starting the scheduler. CSI drivers might have a different procedure, see their documentation on how to customize their limits.

    The limit applies to the entire cluster, so it affects all Nodes.

    FEATURE STATE:

    Dynamic volume limits are supported for following volume types.

    • Google Persistent Disk
    • Azure Disk
    • CSI

    • For Amazon EBS disks on M5,C5,R5,T3 and Z1D instance types, Kubernetes allows only 25 volumes to be attached to a Node. For other instance types on , Kubernetes allows 39 volumes to be attached to a Node.

    • On Azure, up to 64 disks can be attached to a node, depending on the node type. For more details, refer to Sizes for virtual machines in Azure.