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 from Tekton Hub to Artifact Hub #5585

Closed
2 of 4 tasks
QuanZhang-William opened this issue Sep 29, 2022 · 2 comments
Closed
2 of 4 tasks

Migrate from Tekton Hub to Artifact Hub #5585

QuanZhang-William opened this issue Sep 29, 2022 · 2 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@QuanZhang-William
Copy link
Member

QuanZhang-William commented Sep 29, 2022

Feature request

This issue tracks the action items and progress of the migration work from Tekton Hub to Artifact Hub.

Background

Based on @jerop's investigation on Artifact Hub (Thanks @jerop 🎆! ) and discussion in the Tekton Hub community, we have decided to migrate to Artifact Hub as the entry point to Tekton Catalogs. 😁

Use case

To summarize the advantages of Artifact Hub:

  • The Artifact Hub is owned by the Cloud-Native Computing Foundation (CNCF), supporting more than 10 types of resources other than Tekton. Tekton can benefit from the better visibility in Artifact Hub.
  • The Artifact Hub has a natural support for the distributed catalog repository model proposed in TEP-0115, including repo registration and ownership claim features that are not supported in the Tekton Hub.
  • The Artifact Hub supports 2 support tiers for the packages: Verified Publisher and Official Status and displays corresponding badges in the UI. This feature is required in TEP-0079 but not yet supported in the Tekton Hub.
  • The Artifact Hub supports image scanning for Common Vulnerabilities and Exposures (CVEs). This feature is required in TEP-0079 but not supported in the Tekton Hub yet.
  • Other advantages include email notification, metrics, scalability, authentication, licensing... Details can be found in the Tekton Hub vs Artifact Hub (Thanks again @jerop 🙇 !)

Migration Status

Based on the discussion in the Tekton Hub community, we've agreed on the following plan:

  • The Tekton community will continue maintaining the current instance of Tekton Hub(i.e. https://hub.tekton.dev/) until all the dependencies are migrated to Artifact Hub. We will deprecate https://hub.tekton.dev/ after the migration (timeline TBD).
  • The Tekton community will be mainly focusing on contributing to Artifact Hub. All the new features will ONLY be supported in Artifact Hub (e.g. features requested in TEP-0079)
  • As per discussion with @vdemeester and @PuneetPunamiya in the WG, the Tekton Hub repository will be mainly maintained by the RedHat team (but of course, community help is still welcomed 😄 ).

Migration Breakdown

  • Support git-based versioning for Tekton packages in Artifact Hub
  • Add support in Hub Resolver to resolve resources from Artifact Hub.
    • TODO: details to be added in in TEP-0115
  • Support tkn hub CLI to resolve resources from Artifact Hub.
    • TODO: to be tracked in another FR
  • Send out emails/notifications in the Tekton community to identify and migrate other usages of Tekton Hub APIs.
@QuanZhang-William QuanZhang-William added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 29, 2022
@QuanZhang-William
Copy link
Member Author

/assign @QuanZhang-William

@QuanZhang-William
Copy link
Member Author

moving this issue to Hub repo: tektoncd/hub#667 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Done
Development

No branches or pull requests

1 participant