NVMe clusters default to add a hidden node where backups are pulled from. This is due to the reduced durability of NVMe volumes. In cases where durability isn't a concern, I would like to disable backups and remove the hidden node altogether.

The UI currently provides the ability to stop backups by modifying the backup policies (see attachment). However, I cannot remove the hidden node which is simply incurring extra cost.

Obviously there would need to be a major warning provided to the user, but this is not unprecedented in industry. AWS has spot instances that are quite successful.

My use case involves pulling data from Kafka, making it queryable, and storing it for a short period of time (TTL indexed). It's not the end of the world if this data goes away because the nature of the data is such that useful data will come again.