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.

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

Linodes currently can only mount 7 volumes PVCs, not 8 #154

Closed
4 tasks done
rsienko opened this issue Jan 26, 2024 · 5 comments · Fixed by #152
Closed
4 tasks done

Linodes currently can only mount 7 volumes PVCs, not 8 #154

rsienko opened this issue Jan 26, 2024 · 5 comments · Fixed by #152

Comments

@rsienko
Copy link
Contributor

rsienko commented Jan 26, 2024

General:

  • Have you removed all sensitive information, including but not limited to access keys and passwords?
  • Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

Feature Requests:

  • Have you explained your rationale for why this feature is needed?
  • Have you offered a proposed implementation/solution?

Bug Reporting

Linodes need a boot disk, hence maximum PVCs is currently 7.

Expected Behavior

Kubernetes scheduler should not try to assign more than 7 volumes to a single Linode.

Actual Behavior

CSI node advertises that it can bind 8 volumes. This eventually results in pod failing to run when it tries to bind 8th volume on the node.

Steps to Reproduce the Problem

It's not deterministic, but the following is likely to reproduce:

  1. Prepare 3 nodes with no bound PVCs.
  2. Create a StatefulSet, single replica, 7 volumes. This pod should run.
  3. Create another StatefulSet, many replicas, each single volume. Try to bind 21 to 24 volumes in total.
  4. Eventually, a pod will be scheduled on a node trying to bind 8th volume and it will fail to run.

Environment Specifications

Screenshots, Code Blocks, and Logs

Additional Notes


For general help or discussion, join the Kubernetes Slack team channel #linode. To sign up, use the Kubernetes Slack inviter.

The Linode Community is a great place to get additional support.

@codestation
Copy link

Can this be reopened? This change was lost when v0.7.0 was merged and i am getting AttachVolume.Attach failed for volume "pvc-xxxxxxxxxxx" : rpc error: code = ResourceExhausted desc = max number of volumes (8) already attached to instance constantly, so my deployments always gets stuck. The nodes already has 7 volumes attached (plus a boot volume).

@unn
Copy link
Member

unn commented Jul 2, 2024

@nesv for vis

@nesv
Copy link
Contributor

nesv commented Jul 2, 2024

@codestation Could you please open a new issue? That way we can track it appropriately against any potential bug fixes.

@codestation
Copy link

Opened #182 as requested.

@nesv
Copy link
Contributor

nesv commented Jul 2, 2024

Opened #182 as requested.

Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants