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

Support migrating VMs between Proxmox nodes #270

Open
thombohlk opened this issue Oct 16, 2024 · 1 comment
Open

Support migrating VMs between Proxmox nodes #270

thombohlk opened this issue Oct 16, 2024 · 1 comment

Comments

@thombohlk
Copy link

Feature Request

Description

While trying out the tool I noticed that VMs that have disk attached through proxmox-csi-plugin cannot be migrated anymore. Proxmox complains that the disks are owned by a different VM, namely the non-existent VM 9999. I searched if there was some way to force Proxmox to migrate the VM, but I could not find anything. I could only find ways that included a lot of manual work and downtime for the VM that will be migrated, which is not desirable.

Then I realized that even if Proxmox allowed the migration, this will probably mess up the administration of the PVs for the proxmox-csi-plugin. The volumeHandle and the nodeAffinity would not be correct anymore.

So my question/feature request is, would there be any way to support migrating VMs with disks provisioned by proxmox-csi-plugin? Ideally without any downtime to VM and/or pods, but if this is required than at least in an automated fashion and with minimal downtime.

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request

PS. Thank you for this awesome project, integrating Kubernetes with Proxmox is a great idea and the implementation works really really well.
@thombohlk thombohlk changed the title Support VMs to be migrated between Proxmox nodes Support migrating VMs between Proxmox nodes Oct 16, 2024
@sergelogvinov
Copy link
Owner

Hi, I hope you have found the answer already. I wanted to share some information about the limitations of Kubernetes and Proxmox. Kubernetes has values that cannot be changed after they are set. Proxmox can only move the VM if the disk is part of that VM.

In Kubernetes, PV/PVC is not part of the VM. That’s why the disk ID is 9999. There is no way to rename the disk either. The name of the block disk is the ID of the PV in Kubernetes, and there is no metadata for the block device — only the name.

Lastly, Kubernetes has a feature called node drain. It moves the pod to a different place. This is the main idea of Kubernetes.
During VM migration, you may have noticed a performance issue. It seems like VM migration might not be the best option for what you need.

PS. Please let me know why you need VM migration if you feel it is important for your situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thombohlk @sergelogvinov