Move away from minio, possibly to garagehq

Steps to reproduce

MinIO has repeatedly made consistent moves that indicate they are in the process of abandoning the FLOSS minio codebase

• they've decided to suddenly drop a big portion of the web UI which removed all self-serving possibilities for our bucket users https://github.com/minio/minio/issues/21584
• they suddenly stopped publishing docker containers without telling anybody https://github.com/minio/minio/issues/21647#issuecomment-3418675115
  • This for us has a serious implication: we're running a version that's currently affected by a known CVE and there is no more prospects of getting an update to fix this

When did this start?

some months ago (see list of issues above). but the CVE that won't be fixed is fresh from the week of october 20th 2025

Possible fixes

Migrate away from minio and use our next best contender in alternatives. The current choice is set on Garage

process / progress

• review TPA-RFC-56 and prepare MR to change its minio-specific details to garage instead
• review TPA-RFC-84 objectives and prepare MR to adapt it to using garage instead
• adjust list of goals in #41415
• prepare a MR on the wiki page service/object-storage to document procedures using garage instead of minio
• deploy garage on a first VM
• deploy and test web UI for garage
• organize a skill sharing session with TPA to show how things will differ from minio to garage
• move all objects from minio-01 to garage cluster and hook up gitlab to garage cluster instead
• then we can close this issue and continue on with the backup plan in #41415

/cc @anarcat