-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Documentation for dynamic volume limits based on node type #8871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
k8s-ci-robot
merged 5 commits into
kubernetes:release-1.11
from
gnufied:fix-volume-limit-docs
Jun 19, 2018
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| --- | ||
| reviewers: | ||
| - jsafrane | ||
| - saad-ali | ||
| - thockin | ||
| - msau42 | ||
| title: Node-specific Volume Limits | ||
| content_template: templates/concept | ||
| --- | ||
|
|
||
| {{% capture overview %}} | ||
|
|
||
| This page describes the maximum number of volumes that can be attached | ||
| to a node for various cloud providers. | ||
|
|
||
| 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. | ||
|
|
||
| {{% /capture %}} | ||
|
|
||
| {{% capture body %}} | ||
|
|
||
| ## Kubernetes default limits | ||
|
|
||
| The Kubernetes scheduler has default limits on the number of volumes | ||
| that can be attached to a node: | ||
|
|
||
| <table> | ||
| <tr><th>Cloud service</th><th>Maximum volumes per node</th></tr> | ||
| <tr><td><a href="https://aws.amazon.com/ebs/">Amazon Elastic Block Store (EBS)</a></td><td>39</td></tr> | ||
| <tr><td><a href="https://cloud.google.com/persistent-disk/">Google Persistent Disk</a></td><td>16</td></tr> | ||
| <tr><td><a href="https://azure.microsoft.com/en-us/services/storage/main-disks/">Microsoft Azure Disk Storage</a></td><td>16</td></tr> | ||
| </table> | ||
|
|
||
| ## Custom limits | ||
|
|
||
| You can change these limits by setting the value of the | ||
| `KUBE_MAX_PD_VOLS` environment variable, and then starting the scheduler. | ||
|
|
||
| Use caution if you set a limit that is higher than the default limit. Consult | ||
| the cloud provider's documentation to make sure that nodes can actually support | ||
| the limit you set. | ||
|
|
||
| The limit applies to the entire cluster, so it affects all nodes. | ||
|
|
||
| ## Dynamic volume limits | ||
|
|
||
| {{< feature-state state="alpha" for_k8s_version="v1.11" >}} | ||
|
|
||
| Kubernetes 1.11 introduces dynamic volume limits based on node type. This | ||
| is an alpha feature that supports these services: | ||
|
|
||
| - Amazon EBS | ||
| - Google Persistent Disk | ||
|
|
||
| To enable dynamic volume limits, use the `AttachVolumeLimit` flag. | ||
|
|
||
| When the dynamic volume limits feature is enabled, Kubernetes automatically | ||
| determines the node type and supports the appropriate number of attachable | ||
| volumes for the node. For example: | ||
|
|
||
| * On | ||
| <a href="https://cloud.google.com/compute/">Google Compute Engine</a>, | ||
| up to 128 volumes could be attached to a node, depending on the node type. | ||
|
|
||
| * For Amazon EBS disks on M5/C5 instance types, Kubernetes would permit only 25 | ||
| volumes to be attached to a node. For other instance types on | ||
| <a href="https://aws.amazon.com/ec2/">Amazon Elastic Compute Cloud (EC2)</a>, | ||
| Kubernetes would permit 39 volumes to be attached. | ||
|
|
||
| {{% /capture %}} | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
AttachVolumeLimita new feature gate to be documented in the reference?