Michael Steven Fruchtman

Tried that. Existing check in install.sh for current install blocks use of install.sh as an upgrade method. ``` if kubectl get deployment olm-operator -n ${namespace} > /dev/null 2>&1; then echo...

A "-u, --upgrade" flag would certainly be in the style of other script based installer like Python pip with self-update features.

Applications that automatically choose a VolumeSnapshotClass for snapshots are supposed to use StorageClass provisioner field to match or at least contain the same value in VolumeSnapshotClass driver field. And this...

That is odd. A CSI driver has to register a provisioner string. That implies that when the CSI driver was installed the provisioner string was set to everest-csi-provisioner instead of...

Backup failure caused by unintended consequences that set a context deadline from internal changes. Resolved internally. Retry with upstream velero succeeds. [bundle-2024-10-23-15-47-30.tar.gz](https://github.com/user-attachments/files/17498916/bundle-2024-10-23-15-47-30.tar.gz) The issue about excessive datamover pods running doing...

@Madhu-1 Thanks for the update. So that would be Ceph 20? Can't find a codename for it at the moment.

Closed due to stale.

Updated issue definition to include addition objects found to also be created by concatenating other object names. DataUpload (includes name of Backup) DataDownload (includes name of Restore)

VolumeSnapshotContent objects are not namespaced. The logging is to indicate the VolumeSnapshot's namespace. This is similar to the relationship of PVC and PV. During backup the VolumeSnapshot is moved to...

I will need to check what part of the puzzle is responsible for setting a SourceVolumeMode whether the external-snapshotter or the CSI driver. The lack of SourceVolumeMode still would have...