-
Notifications
You must be signed in to change notification settings - Fork 296
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
Add data disks not present in VM template to VM during cloning #3213
Comments
Note: one thing we should check at least once manually or in an e2e test: make sure that deletion does also delete the additional disk, so we don't leak data/vmdk's. |
CC @lubronzhan , @neolit123 , this one might be interesting to you folks :-) |
i'm not aware of related FR but happy to help with review on any PRs. |
It is WIP by @vr4manta at: 👍 |
Yes. I'm working this one as a feature we are needing. I've done a first pass at this and all is working so far. I've fixed some tests to make sure the conversion works properly. I've also verified that when the VM is deleted, the disks are also cleaned up. Thanks! |
/kind feature
Describe the solution you'd like
As a cluster admin, I would like to create machines with additional data disks so that I can have dedicated disks for such things as etcd, container runtime, image storage, swap, etc.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The idea here is to add new disks to a VM during the clone process that are not part of the vSphere VM Template. This way we can share one template across multiple machine sets but tweak the additional data disks across each machine set based on the needs of that group.
Initial goal is to support the govmomi mode.
Currently most vSphere VM Templates have a single defined disk for the OS. This feature should still check to see if any other disks are present in template and make sure new data disks are added.
There currently is a property
additionalDisksGiB
that will change the size of existing disks found in the vSphere VM Template, but is not related to adding disks not present in the template. This may cause confusion. Current proposal is to have a new field that will start simple and grow over time w/ additional capabilities. One example would be to have new disks only use same controller (usually scsi controller) as the primary disk.Environment:
kubectl version
): 1.30.3/etc/os-release
): Red Hat Enterprise Linux CoreOS 418The text was updated successfully, but these errors were encountered: