Implement Custom PVC Rollback Solution for Failed Updates in Unsupported Storage Classes

[Heavybullets8]

Description

Following the recent update to Dragonfish, which removed support for OpenEBS CSI in TrueNAS SCALE ix applications, our ability to backup and restore PVCs using the ix API has been impacted. This issue is critical for handling rollbacks after failed updates, ensuring both applications and their data can be reverted to their previous stable states.

Objective

• Develop a PVC rollback solution: Create a system that not only backs up PVCs but also allows us to rollback these snapshots to recover from failed updates. This system should either integrate with the TrueNAS SCALE rollback API or be a custom-built solution, depending on what's more feasible.

Requirements

• Explore TrueNAS SCALE Rollback API: Determine if we can leverage the existing TrueNAS API for rollbacks and integrate it with our PVC backup system.
• Design and Testing: If a custom solution is needed, design one that ensures seamless rollbacks and test it extensively to guarantee reliability.
• Ensure Compatibility: The solution should work smoothly with our existing infrastructure and applications dependent on persistent storage.

Notes

• Insights or suggestions from the community on leveraging TrueNAS features or on custom rollback solutions would be greatly appreciated.
• This is a wish-list item at the moment. No grantee that this will be added, although I am attempting to configure the backup and restore class to allow for this, implementation may be too complicated to implement and more importantly, maintain..

[Heavybullets8]

https://github.com/Heavybullets8/heavy_script?tab=readme-ov-file#archived-repository-notice