Feedback for New Must-Gather

[shubham-pampattiwar]

Consider the following enhancements/requests:

• Add provider to BSL table
• Add some backup spec flags like defaultVolumesToFSBackup , snapshotMoveData` etc
• Refrain from adding Velero DownloadRequest CRs to the summary markdown, they are usually a lot and are ephemeral, velero cleanup them up.
• CRD version

cc: @weshayutin @mateusoliveira43

[weshayutin]

@sseago

• find the md5sum hash of production CRD's for OADP / Velero
  • flag any md5sum mismatch on the cluster w/ expected sums?

[weshayutin]

@shubham-pampattiwar

• add the backup type as a column in the markdown

[sseago]

@weshayutin we'd have to test that md5sum is predictable enough -- i.e. will cluster differences in how the output is generated change anything? Probably can't just compare md5sum with the yaml from github, though -- may need to store md5sum generated from a cluster install.

[PrasadJoshi12]

Maybe we could just print the phase in status.Phase column instead of status phase completed.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale