Repin MinIO functional-test mock to quay.io

[CRThaze]

What

Repoint the MinIO S3 mock used by the s3 and multi-backend functional legs from docker.io/minio/minio to quay.io/minio/minio, and drop the --console-address flag.

Why

MinIO removed its community images from Docker Hub recently, so minio/minio:RELEASE.2025-03-12T18-04-18Z now 404s:

Failed to pull image "minio/minio:RELEASE.2025-03-12T18-04-18Z":
  pull access denied, repository does not exist or may require authorization:
  server message: insufficient_scope: authorization failed

Both MinIO-backed legs fail at Deploy mock backends (ImagePullBackOff) before s3proxy is even installed. These same fixtures passed on 2026-09-03; the break is purely the upstream image going away, so every chart PR is now red on these two legs. MinIO still publishes the images on quay.io.

--console-address is removed because newer community builds have no embedded console (the flag can make a current tag fail to start), and the tests only use the S3 API + /minio/health/ready — so it is unneeded and this keeps the mock working across releases.

Scope

Test fixture only (not under charts/s3proxy/), so no Chart.yaml version bump. The ci/functional/** path still triggers the functional workflow, which is the verification.

[github-actions]

📊 Helm Render Diff Summary

Chart charts/s3proxy rendered with Kubernetes 1.29.0. Informational only — this check never fails the PR.

Values File	Chart Path	Changes	Status
test-values/auth-existing-secret.yaml	charts/s3proxy	-	✅ No Changes
test-values/autoscaling.yaml	charts/s3proxy	-	✅ No Changes
test-values/azureblob-existing-secret.yaml	charts/s3proxy	-	✅ No Changes
test-values/azureblob-managed-identity.yaml	charts/s3proxy	-	✅ No Changes
test-values/azureblob.yaml	charts/s3proxy	-	✅ No Changes
test-values/b2.yaml	charts/s3proxy	-	✅ No Changes
test-values/filesystem.yaml	charts/s3proxy	-	✅ No Changes
test-values/gcs.yaml	charts/s3proxy	-	✅ No Changes
test-values/ingress.yaml	charts/s3proxy	-	✅ No Changes
test-values/multi-backend.yaml	charts/s3proxy	-	✅ No Changes
test-values/openstack-swift.yaml	charts/s3proxy	-	✅ No Changes
test-values/rackspace.yaml	charts/s3proxy	-	✅ No Changes
test-values/s3.yaml	charts/s3proxy	-	✅ No Changes
test-values/tls-existing-secret.yaml	charts/s3proxy	-	✅ No Changes
test-values/tls.yaml	charts/s3proxy	-	✅ No Changes
test-values/transient.yaml	charts/s3proxy	-	✅ No Changes

🎉 No changes detected in any of the tested configurations!