You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow specifying the following attributes on the data_disk block of the spotinst_stateful_node_azure resource.
create_option
source_resource_id
on_demand_bursting_enabled
disk_iops_read_write
Use Cases
The main benefit of stateful nodes is the ability to persist the os and data disks. However, the current implementation only allows you to begin from an empty disk. It would be nice to be able to set the create option and source resource id to allow cloning from an existing snapshot/disk. Additionally, configurations like on demand bursting and iops read/write can't be specified when deploying via terraform.
I recognize you can import_vm's which would theoretically enable a lot of this but, if you deployed the vm's you're importing via terraform then it results in breaking the state of that deployment once spot kills the existing vm.
Terraform Version
1.4.2
Description
Allow specifying the following attributes on the
data_disk
block of thespotinst_stateful_node_azure
resource.create_option
source_resource_id
on_demand_bursting_enabled
disk_iops_read_write
Use Cases
The main benefit of stateful nodes is the ability to persist the os and data disks. However, the current implementation only allows you to begin from an empty disk. It would be nice to be able to set the create option and source resource id to allow cloning from an existing snapshot/disk. Additionally, configurations like on demand bursting and iops read/write can't be specified when deploying via terraform.
I recognize you can import_vm's which would theoretically enable a lot of this but, if you deployed the vm's you're importing via terraform then it results in breaking the state of that deployment once spot kills the existing vm.
Potential Terraform Configuration
References
Community Note
The text was updated successfully, but these errors were encountered: