Quiesce jobs for Medusa and Reaper

[mieslep]

What is missing? At times, it may desirable to quiesce Medusa and/or Reaper. I'd like to be able to submit a job document to quiesce (or resume) both Medusa and Reaper - basically pausing and resuming any scheduled activities they have. The job status (in YAML) should update to reflect the state of quiescence or resumption.

Why do we need it? This could be because they are having a suspected negative impact on cluster performance, or (in the case of Medusa) it cannot handle renewed Cassandra CA certificates being rolled through the cluster.

Environment

• K8ssandra Operator version:

  v1.2.1Anything else we need to know?:

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-215

[adejanovski]

For Medusa:

you can pause Medusa schedules by setting .spec.disabled=false in your MedusaBackupSchedule object. There's no way we can pause an ongoing backup, which only a rolling restart could do (the medusa container can be restarted without restarting the whole pod).

For Reaper:

You'll have to either pause the repair schedules in the UI or through the Rest API. Reaper doesn't (yet) interact with any CRD.