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

Pod failed to startup due to Volume attach limitations #405

Open
RolandMa1986 opened this issue Apr 16, 2021 · 1 comment
Open

Pod failed to startup due to Volume attach limitations #405

RolandMa1986 opened this issue Apr 16, 2021 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@RolandMa1986
Copy link

What happened:
Pod failed to startup due to Volume attach limitations. But the Pod shouldn't be scheduled to the Node that has already attached 10 drivers.

What you expected to happen:
Pods should be scheduled to a node that has less than 10 drivers attached.

Anything else we need to know?:
The /data folder that attached to the node is counted already. So only 9 volumes can be attached through qingcloud-csi driver.

20210416172303

Environment:

  • QKE version: v3.0.0
@RolandMa1986 RolandMa1986 added the kind/bug Categorizes issue or PR as related to a bug. label Apr 16, 2021
@hlwanghl hlwanghl added this to the v3.1.0 milestone Apr 16, 2021
@hlwanghl
Copy link
Contributor

https://github.com/kubesphere/helm-charts/blob/0f4154c2f771f936d00810c39f2910ab55be6b90/src/test/csi-qingcloud/values.yaml#L32

Need update csi-qingcloud chart to allow different settings for different volumes, i.e. max 10 standard/ssd volumes, max 50 neonsan volumes, per node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants