Velero provides the means of fine tuning what is included in a backup via label selections and namespaces

Focus is on ensuring we are good on the Restore for each k8s + ocp resource.  Backups typically are simple and are an export of resource as-is and will generally work...the restore is the tricky part where most errors will show up

1. Assume upstream Velero most likely handles the k8s specifics well
2. We will want to be cautious of new k8s resources recently added, there is a higher likelihood of a new resource being introduced which changes behavior upstream hasn’t yet seen.
3. Will want to track each OCP release to understand what new k8s/ocp resources have been added and ensure we have test coverage for backup/restore scenarios of test apps using those resources.

1. Assume that OpenShift specific resources OCP has ADDED or MODIFIED behavior may require specific help in plugins
2. Our Velero OpenShift plugins are here:
   1. https://github.com/openshift/openshift-velero-plugin/tree/master/velero-plugins