Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Tekton single arch image build to ghcr.io #2221

Open
afrittoli opened this issue Oct 2, 2024 · 0 comments
Open

Migrate Tekton single arch image build to ghcr.io #2221

afrittoli opened this issue Oct 2, 2024 · 0 comments
Labels
Hacktoberfest Categorizes issue as one for Hacktoberfest 2021 kind/feature Categorizes issue or PR as related to a new feature.

Comments

@afrittoli
Copy link
Member

afrittoli commented Oct 2, 2024

Feature request

Migrate the single-arch-template pipeline to publish to ghcr.io. This includes updates to any of the cronjobs that use this template to build images.

Note: To be implemented as a separate PR: update references in the plumbing repo from gcr.io to ghcr.io once the new images are produced.

The pipeline project release pipeline. has been migrated and can provide some insight.

Some key information for the migration:

Use case

Reduce Cloud Storage / Container Registry Spending: #2157

Additional Info

  • the template part defines the pipeline that is executed to build images
  • the cronjobs provide the trigger for the execution of the pipelines, and they include the list of parameters as well as the frequency of execution

The template part needs to be updated so that it may work with ghcr.io. The current version works with gcr.io, and unfortunately, it's not enough to change the target registry as authentication works a bit different (for gcr.io we used a service account file, and for ghcr.io we use a PAT), and ghcr.io requires OCI labels to be set

There are three types of builds we do today, which correspond to three separate templates.

This issue covers updating the template and cronjob for single architecture.

The order of implementation should be:

@afrittoli afrittoli added kind/feature Categorizes issue or PR as related to a new feature. Hacktoberfest Categorizes issue as one for Hacktoberfest 2021 labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hacktoberfest Categorizes issue as one for Hacktoberfest 2021 kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant