See the parent story for more context:

Along with the periodic backup controller that creates the CronJob, we would need to provide the workload or Go command for the CronJob to execute i.e run inside the pod that is created periodically by the CronJob.

This cmd e.g "create-etcdbackup" effectively creates a new `operator.openshift.io/v1alpha1 EtcdBackup` CR via the following workflow:

• Read the Backup CR to get the pvcName (and anything else) required to populate an `EtcdBackup` CR. Or easier yet the periodic controller can simply set all the required inputs to this command in the CronJob's container spec. 

• Create the `operator.openshift.io/v1alpha1 EtcdBackup` CR. The CR name should be the same as the Job instance that's running the cmd. The cmd should also set the ownerRef of the CR to be that Job. That information can be exposed to the cmd via envvars on the Job's metadata fields.