Remove gcr.io from supporting container registry for PipeCD artifact
Open
@rahulshendre is already working on this.
Since Sep 17, 2026.
kind/enhancement
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What would you like to be added:
Remove the gcr.io from support container registry for PipeCD artifact
Why is this needed:
Up to now, moved all the artifact of the PipeCD project to ghcr (including container image and chart artifact). There are still some artifacts that also being pushed to gcr because the workload like GCP Cloud Run strictly required container image to be hosted in GCR. After the migration from GCR to GAR (Artifact Registry), there is no more strict requirement like that, removing the gcr.io from supporting container registry would help us reduce the maintaining cost and infrastructure resources.
TODO
- Update workflow to remove gcr artifact pushing <- @khanhtc1202
- Update docs (dev, v1 and latest release) to remove the gcr mentioned container image
- Ensure to not using the gcr.io/pipecd/helloworld container image in test, playing environment <- @rahulshendre
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.