PVC AttachVolume.Attach Failed - Maximum number of block storage volumes are attached

Hey all,

We've been using linode LKE for the past few months and have recently run into this error being reported when running up new pods as soon as any single node hits the maximum number of storage volumes to it:

attachdetach-controller  AttachVolume.Attach failed for volume "pvc-a980a27661144deb" : rpc error: code = Internal desc = error attaching volume: [400] Maximum number of block storage volumes are attached to this Linode, please resize Linode to be larger to attach more volumes

Is there any way to force the kube-scheduler to take into account the number of PVC's when it's assigning workloads to nodes instead of assigning it only to find out it can't start afterwards?

Our current workarounds are pretty fragile:

  1. Delete the pod repeatedly until it moves
  2. Use nodeSelector to manually assign it to a node

1 Reply

Is there any way to force the kube-scheduler to take into account the number of PVC's when it's assigning workloads to nodes instead of assigning it only to find out it can't start afterwards?

There is not a way for this to be done without some larger changes to the kube-scheduler on our side, but I've passed along your specific request to be considered during any discussions around changes or improvements to our LKE service in the future.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct