fix(manifests): update MinIO image registry

[CodeWith-sakib]

What this PR does:

Updates the MinIO image used by the Control Plane and PipeCD manifests to use the Quay registry and a newer MinIO release.

Why we need it:

The existing minio/minio:RELEASE.2020-08-26T00-00-49Z image can no longer be pulled from Docker Hub, causing make run/controlplane to fail with ImagePullBackOff.

This change switches the image to:

quay.io/minio/minio:RELEASE.2024-12-18T13-15-44Z

The image was verified locally and the Control Plane was successfully deployed on a kind cluster.

Which issue(s) this PR fixes:

Fixes #7380

Does this PR introduce a user-facing change?:

• How are users affected by this change: Users running the Control Plane locally can successfully pull the MinIO image and start the Control Plane.
• Is this breaking change: No.
• How to migrate (if breaking change): Not applicable.

Screenshots/Videos (for documentation or website changes):

Not applicable. This PR does not modify documentation or website files.

Verification

Verified the Control Plane deployment on a local kind cluster after applying the changes. All required services are running successfully:

[netlify]

✅ Deploy Preview for pipecd-site canceled.

Name	Link
🔨 Latest commit	1106b60
🔍 Latest deploy log	https://app.netlify.com/projects/pipecd-site/deploys/6aaaf339e2657b0008b1d5d4

[Copilot]

🟡 Changes recommended

The committed quickstart manifest still uses the old Docker Hub MinIO image and must be regenerated.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Updates MinIO images in the PipeCD and Control Plane manifests to use Quay and a newer release.

Changes:

• Switches MinIO from Docker Hub to Quay.
• Updates the MinIO release tag in both Helm charts.
• The committed quickstart manifest still requires regeneration.

File summaries

File	Description
manifests/pipecd/values.yaml	Updates MinIO version.
manifests/pipecd/templates/deployment.yaml	Uses the Quay MinIO image.
manifests/controlplane/values.yaml	Updates MinIO version.
manifests/controlplane/templates/deployment.yaml	Uses the Quay MinIO image.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[harshitghagre]

Pod is running fine, one thing though the deployment still uses MINIO_ACCESS_KEY and MINIO_SECRET_KEY. They work, but minio logs a warning asking to switch to MINIO_ROOT_USER and MINIO_ROOT_PASSWORD. Also, any reason for not using the newer RELEASE.2025-09-07T16-13-09Z?

[CodeWith-sakib]

Hey @harshitghagre, Thanks for pointing this out. I chose RELEASE.2024-12-18T13-15-44Z because it is the version referenced by MinIO's Helm configuration with the quay.io/minio/minio registry, and it supports both amd64 and arm64. I also verified it successfully with the PipeCD Control Plane locally.

I can also verify RELEASE.2025-09-07T16-13-09Z with the Control Plane and use the newer version if it works correctly. I'll also update the deprecated MINIO_ACCESS_KEY and MINIO_SECRET_KEY variables to MINIO_ROOT_USER and MINIO_ROOT_PASSWORD.