anchor.diff:  ....
   
   The scheduled tasks will (these are just for fast results, not recommended for production):
  -  * take a backup every minute using pgBaseBackup
  -  * take a full pgBackRest backup every even minute
  -  * take a diff pgBackRest backup every odd minute
  +
  +* take a backup every minute using pgBaseBackup
  +* take a full pgBackRest backup every even minute
  +* take a diff pgBackRest backup every odd minute
   
   View the logs for the `scheduler` pod until the tasks run:
   
  
positive.code: delete the task.
  
  See the following examples for creating config maps that Crunchy Scheduler can parse:
  * link:https://github.com/CrunchyData/crunchy-containers/blob/scheduler/examples/kube/scheduler/configs/schedule-backrest-diff.json[pgBackRest Diff Backup]
  * link:https://github.com/CrunchyData/crunchy-containers/blob/scheduler/examples/kube/scheduler/configs/schedule-backrest-full.json[pgBackRest Full Backup]
  * link:https://github.com/CrunchyData/crunchy-containers/blob/scheduler/examples/kube/scheduler/configs/schedule-pgbasebackup.json[pgBaseBackup Backup]
  
negative.code: ==== pgBackRest Schedules
  
  To configure Crunchy Scheduler to create pgBackRest backups the following is required:
  
  * pgBackRest schedule definition requires a deployment name.  The PostgreSQL pod should be created by a deployment.
  
  ==== pgBaseBackup Schedules
  
  To configure Crunchy Scheduler to create pgBaseBackup scheduled backups, the following is required:
  
  * The name of the secret that contains the username and password the Scheduler will use to
    configure the job template.  See link:https://github.com/CrunchyData/crunchy-containers/blob/scheduler/examples/kube/scheduler/primary/secret.json[the primary secret example].
    for the structure required by the Scheduler.
  * The name of the PVC created for the backups.  This should be created by the user prior to scheduling the task.
  
  ==== Kubernetes and OpenShift
  
  