Demolish storage workarounds #43

Closed
opened 2024-08-16 21:33:35 +00:00 by rasmus · 1 comment
Owner

The current situation has grown out of hand, with VMs having multiple large volumes, some cannot tolerate non-node-local storage.

The local storage disrupts regular updates to Proxmox, and as such degrades service to others. Nodes can't be shut down without downtime, local storage can't be migrated (insufficient free storage).

@eaas has worked on this with Proxmox CSI.

The current situation has grown out of hand, with VMs having multiple large volumes, some cannot tolerate non-node-local storage. The local storage disrupts regular updates to Proxmox, and as such degrades service to others. Nodes can't be shut down without downtime, local storage can't be migrated (insufficient free storage). @eaas has worked on this with Proxmox CSI.
Owner

removed storage workers but moved back other nodes to local storage - iops is too scarse on nas.
just shut down the kube workers on the node being rebooted.

removed storage workers but moved back other nodes to local storage - iops is too scarse on nas. just shut down the kube workers on the node being rebooted.
eaas closed this issue 2024-09-08 19:49:41 +00:00
Sign in to join this conversation.
No Label
new app
greenlit
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: k-space/kube#43
No description provided.