Reduce Cloud Storage / Container Registry Spending

[afrittoli]

Steps to adopt ghcr.io

• [ ] Make the list of regions configurable
• [ ] Setup auth for ghcr.io
  • Look into https://github.com/octo-sts/app as an option
• [ ] Add logic to link container images to projects
• [ ] Update runtime resource with image registry values for ghcr.io

[afrittoli]

This will have to be done for various Tekton projects. The set relevant for the tekton-releases project is:

• [x] Pipeline
  • Regions configurable: https://github.com/tektoncd/pipeline/pull/8246
  • Auth for ghcr.io: https://github.com/tektoncd/pipeline/pull/8251
  • Link images to project: https://github.com/tektoncd/pipeline/pull/8247
  • Update runtime resources: https://github.com/tektoncd/plumbing/pull/2158
• [x] Triggers
  • Changes in triggers: https://github.com/tektoncd/triggers/pull/1767
  • Changes in plumbing: https://github.com/tektoncd/plumbing/pull/2206
• [x] Chains
  • Changes in chains: https://github.com/tektoncd/chains/pull/1220
  • Changes in plumbing: https://github.com/tektoncd/plumbing/pull/2226
• [ ] Results
• [x] Dashboard
  • Changes in dashboard: https://github.com/tektoncd/dashboard/pull/3634
  • Changes in plumbing: https://github.com/tektoncd/plumbing/pull/2202
• [ ] Operator
• [ ] Cli
  • [ ] Currently built from the plumbing repo
  • [ ] All plumbing images will be moved to ghcr.io in https://github.com/tektoncd/plumbing/issues/2223
  • [ ] Add a build in the cli repo that uses ghcr.io

For tekton-nightly there are more projects that publish images to gcr.io, however, the egress bandwidth for those is not significant (< 10% of tekton-releases).

[afrittoli]

Migrate catalog bundles to ghcr.io: https://github.com/tektoncd/plumbing/pull/2220