Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Populate MaxVolumesPerNode in NodeGetInfoResponse #39

Closed
leakingtapan opened this issue Oct 3, 2018 · 1 comment · Fixed by #289
Closed

Populate MaxVolumesPerNode in NodeGetInfoResponse #39

leakingtapan opened this issue Oct 3, 2018 · 1 comment · Fixed by #289
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone
0.4

Comments

@leakingtapan
Copy link
Contributor

This is to help CO to decide how many volume maximum could be attached to the node without going over the limit.

Reference:
https://github.com/container-storage-interface/spec/blob/master/spec.md#nodegetinfo
@leakingtapan leakingtapan added this to the 0.3-beta milestone Oct 3, 2018
@leakingtapan
Copy link
Contributor Author

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 16, 2018
@leakingtapan leakingtapan added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Nov 16, 2018
@leakingtapan leakingtapan modified the milestones: beta, GA Feb 21, 2019
@bertinatto bertinatto mentioned this issue May 3, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
0.4
Development

Successfully merging a pull request may close this issue.

Add max number of volumes that can be attached to an instance bertinatto/aws-ebs-csi-driver
2 participants
@leakingtapan @k8s-ci-robot