Move backup/restore to the Charm

[kimwnasptd]

Context

similarly to canonical/mlmd-operator#80

Right now our backup/restore guide has the following issues

1. It has manual commands the user needs to run to push the data to S3 (rclone)
2. Users need to download binaries to parse the secret-key and download the data locally (rclone)
3. The data needs to go via the host-machine that runs the rclone command, for which we use kubectl port-forward

We should move all of this logic to the Charm, to ensure users don't need to install any binaries and the data will go directly from the Charm to S3

What needs to get done

1. Include all needed binaries (or python libraries) for backup to the Charm
2. Have an action that pushes the buckets of MinIO to another S3

Definition of Done

1. Have a spike to confirm our understanding of rclone sync, and which files it copies
2. Have a spike to discuss if we want to copy all files, or ones that fit a timeframe (could get field input)
3. The action can be executed in an airgap environment
4. Users don't need to run any other commands from their machine
5. The data will go directly to the S3 from the Charm

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5625.

This message was autogenerated