The Tekton Catalog is a centralized repository of reusable Task and Pipeline resources designed for the Tekton Pipelines continuous integration and delivery platform on Kubernetes. Written primarily in Shell, the repository serves as a comprehensive collection of pre-built automation components that developers and operators can integrate into their own Tekton pipelines without building from scratch. Each Task is organized in its own directory with accompanying documentation and Kubernetes manifests, allowing users to selectively install only the components they need on their clusters.
The catalog supports multiple versions of Tekton resources, with the main branch currently aligned with v1beta1 specifications since June 2020, while legacy v1alpha1 resources remain available on a separate branch. Tasks in the catalog are published to Artifact Hub under the tekton-catalog-tasks repository, which serves as the recommended discovery mechanism following the deprecation of the previous Tekton Hub service. Individual tasks are increasingly being published from their own dedicated repositories as part of a broader shift toward a distributed catalog model rather than maintaining a single monolithic repository.
Resources within the catalog include structured metadata such as version labels, minimum pipeline version requirements, associated tags, and display names. The catalog also supports Tekton Bundles, which allow Tasks to be stored as container images in registries rather than as Kubernetes custom resources, enabling users to reference tasks without pre-installation through the bundle resolver. Tasks are available at ghcr.io/tektoncd/catalog/upstream/tasks with specific version tags.
The project is currently undergoing significant structural changes. While not deprecated, the catalog is transitioning from a centralized model to a distributed approach where individual resources are maintained in separate repositories under the tektoncd-catalog organization. This migration reflects evolving best practices in how resources are versioned, maintained, and contributed. The roadmap documents this transition, and the community is actively preparing a Tekton Enhancement Proposal to formalize the new direction and migration path. Contributors are encouraged to engage through GitHub issues and Tekton community meetings as this evolution continues.
