XaverStiensmeier
commented
1 month ago Fixed in dev. See the configurations keys:
bootFromVolume (optional:False)
If True, the instance will boot from a volume created for this purpose. Keep in mind that on demand scheduling can lead to multiple boots of the same configurated node. If you don't make use of terminateBootVolume this will lead to many created volumes.
volumeSize (optional:50)
The created volume's size if you use bootFromVolume.
terminateBootVolume (optional:True)
If True, once the instance is shut down, boot volume is destroyed. This does not affect other attached volumes. Only the boot volume is affected.
Some clouds prefer to use boot volumes instead of space on the instance. Currently, those automatically created volumes are not deleted. That is an issue, because our on demand scheduling can lead to many worker restarts which can lead to many volume creations that are not deleted.