Enhancements

Stork now supports Kubevirt VMs for Portworx backup and restore operations. You can now initiate VM-specific backups by setting the backupObjectType to VirtualMachine. Stork automatically includes associated resources, such as PVCs, secrets, and ConfigMaps used as volumes and user data in VM backups. Also, Stork applies default freeze/thaw rules during VM backup operations to ensure consistent filesystem backups.
Cloud Native backups will now automatically default to CSI or KDMP with LocalSnapshot, depending on the type of schedules they create.
Previously in Stork, for CSI backups, you were limited to selecting a single VSC from the dropdown under the CSISnapshotClassName field. Now you can select a VSC for each provisioner via the CSISnapshotClassMap.
Now, the creation of a default VSC from Stork is optional.

Bug Fixes

Issue: Canceling an ongoing backup initiated by PX-Backup results in the halting of the post-execution rule.
User Impact: This interruption causes the I/O processes on the application to stop or the post-execution rule execution to cease.
Resolution: To address this, Stork executes and removes the post-execution rule CR as part of the cleanup procedure for the application backup CR. #1602
Issue: Generic KDMP backup/restore pods become unresponsive in environments where Istio is enabled.
User Impact: Generic KDMP backup and restore fails in the Istio enabled environments.
Resolution: Relaxed the Istio webhook checks for the stork created KDMP generic backup/restore pods. Additionally, the underlying issue causing job pod freezes has been resolved in Kubernetes version 1.28 and Istio version 1.19. #1623