This spike is to track the todos for `NoConfig` backups

• update the defaults in the Openshift/API
  • currently an empty string for `schedule` will error
  • use the `kubebuilder annotation` to set defaults instead

• settle on defaults on the NoConfig CR
  • consensus over the default configs to be released
     

• Alert for the backups
  • consensus over the default configs to be released

• CEO's statusCondition
  • raise `StatusCondition` describe the status of the NoConfig backups

• backup-server container error handling
  • currently the sidecar container fails upon error. This approach is not accepted, since a failing container will make the whole Pod `not-ready`. This will lead to non-functioning cluster