TEP-0168: Sunset tektoncd/catalog for tektoncd-catalog Distributed Architecture - #1283
TEP-0168: Sunset tektoncd/catalog for tektoncd-catalog Distributed Architecture#1283vdemeester wants to merge 2 commits into
Conversation
tekton-robot
added
the
kind/tep
tekton-robot
added
needs-rebase
…chitecture Propose sunsetting the centralized tektoncd/catalog repository in favor of a fully distributed catalog architecture. Supersedes TEP-0003 and TEP-0079. Key points: - Two-tier model: curated tektoncd-catalog repos (Tier 1) and community-owned catalogs (Tier 2) - Freeze-don't-migrate sunset for tektoncd/catalog - Artifact Hub as the single discovery layer - Template repository and reusable GitHub Actions to make it trivially easy to create and publish catalogs - Keyless signing via Sigstore (Fulcio + Rekor)
ff4a7ee to
7f1be54
Compare
tekton-robot
removed
the
needs-rebase
afrittoli
left a comment
afrittoli
left a comment
There was a problem hiding this comment.
Thanks for this! It looks good to me.
The trust signals on ArtifactHub are really a key aspect.
The "Official"one can be reserved to cases where the code wrapped by the tasked is maintained by the author of the task.
The Tekton Community maintained tasks may not be easy to identify from the trust signal alone, but actually that's not that important, if a Task it's high quality and maintained that's all that matters.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
tekton-robot
added
the
approved
- Remove orphaned CLI Scaffolding TOC entry (no section exists) - Reconcile signing requirement: MUST for Tier 1 graduation, not a gate for initial Tier 2 adoption - Clarify multi-resource Artifact Hub registration - Fix reference link formatting (one per line) - Add explicit dependency: archive only after graduation complete
savitaashture
left a comment
savitaashture
left a comment
There was a problem hiding this comment.
👏 this gives more space for publishing own tasks without waiting for the review
|
|
||
| #### Tier 1: Curated `tektoncd-catalog` Repositories | ||
|
|
||
| Tier 1 resources live in standalone repositories under the [`tektoncd-catalog`](https://github.com/tektoncd-catalog) GitHub organization. These are first-party, curated resources that the Tekton project actively maintains and dogfoods. |
There was a problem hiding this comment.
any reason to have standalone repository under github
There was a problem hiding this comment.
not sure I understand the question. the idea is to do the same as what we do today with the golang or git-clone repositories (where there is multiple tasks and stepactions 👼🏼).
There was a problem hiding this comment.
The reason is also that this way it can be a different set of maintainers for each repositories as well.
| Each catalog repository includes an `artifacthub-repo.yml` file that configures Artifact Hub integration: | ||
|
|
||
| ```yaml | ||
| repositoryID: <generated-by-ah> |
There was a problem hiding this comment.
can we also mention how to get the repositoryID or any link which explains about this
There was a problem hiding this comment.
imo we can have this in the documentation
There was a problem hiding this comment.
which documentation ?
|
|
||
| Graduate a small set of resources from `tektoncd/catalog` (or confirm existing `tektoncd-catalog/*` repos) as Tier 1: | ||
|
|
||
| Some resources have already graduated to `tektoncd-catalog/*` repositories (e.g., `git-clone`, `kaniko`, `golang-*`). Additional graduation candidates include resources the project dogfoods or plans to dogfood: |
There was a problem hiding this comment.
currently under tektoncd/catalog many tasks follow Tier1 recommendations so just want to understand how are we classifying only set of tasks for Tier1 category 🤔
ex: buildah
There was a problem hiding this comment.
buildah is an example of not a Tier 1 task, it is not used by our dogfooding effort (so far), and it might be better for Red Hat to maintain this (for example, in openshift-pipelines for example). Example of tier 1 would be the oracle cloud tasks, etc..
5 participants
Summary
Propose sunsetting the centralized
tektoncd/catalogrepository in favor of a fully distributed catalog architecture. This TEP supersedes TEP-0003 (Tekton Catalog Organization) and TEP-0079 (Tekton Catalog Support Tiers), building on TEP-0110 and TEP-0115.Core idea: separate discovery (Artifact Hub) from endorsement (whoever maintains the resource).
Key points:
tektoncd-catalog/*repos maintained by active maintainers (Tier 1) and community-owned catalogs anywhere (Tier 2)tektoncd/catalog— archive read-only, pinned references keep workingtekton.dev/deprecatedhiding sunset resources from search/kind tep