logo
Alauda DevOps Pipelines Docs
logo
Alauda DevOps Pipelines Docs
Navigation

Overview

Introduction
Architecture
Feature Overview
Lifecycle Policy
Quick Start
Release Notes

Concepts

TektonConfig
TektonPipeline
Install
Upgrade

Configure

Adjusting Optional Configuration Items of Subcomponents
Configuring Resource Quotas for Pipeline Components
Pod Template Configuration Guide
Regular Cleanup of TaskRun and PipelineRun Resources

How To

Deploying tekton-pipelines in a global cluster through TektonConfig

Pipelines

Introduction
Architecture

Concepts

Tasks
TaskRuns
Pipelines
PipelineRuns
StepActions
Resolvers
Workspaces
Pod Templates
Quick Start
permissions

how_to

Adjust Dockerfile for Building Task-Compatible Custom Images

trouble_shooting

Failed to create pod due to config error when using custom images in Tekton

Triggers

Introduction
Architecture

Core Concepts

Core Concepts
EventListener
Trigger
Interceptor
TriggerBinding
TriggerTemplate
Quick Start

How To

Setup EventListener
Use GitLab Event Triggers
Create TriggerTemplate

Troubleshooting

The Pipeline is not automatically triggered
Permission Description

Hub

Introduction
Architecture

Core Concepts

Concepts
Understanding Tekton Hub
Permission Description

Configure

Tekton Hub Configuration
Adding Custom Catalogs

Tutorials

Creating a Custom Catalog
Writing Tasks for Tekton Hub
Writing Pipelines for Tekton Hub

Results

Introduction
Architecture

Concepts

Core Concepts
Tekton Results
Quick Start
permissions

Configure

Database Configuration

Supply Chain Security

Introduction
Architecture

Concepts

Core Concepts
Understanding Tekton Chains
Quick Start

API Reference

Introduction

Kubernetes APIs

Pipelines

Pipeline [tekton.dev/v1]
Task [tekton.dev/v1]
PipelineRun [tekton.dev/v1]
TaskRun [tekton.dev/v1]
ClusterTask [tekton.dev/v1]
Run [tekton.dev/v1]
CustomRun [tekton.dev/v1]
StepAction [tekton.dev/v1]
VerificationPolicy [tekton.dev/v1alpha1]
ResolutionRequest [resolution.tekton.dev/v1beta1]

Triggers

Trigger [triggers.tekton.dev/v1beta1]
TriggerTemplate [triggers.tekton.dev/v1beta1]
EventListener [triggers.tekton.dev/v1beta1]
TriggerBinding [triggers.tekton.dev/v1beta1]
Interceptor [triggers.tekton.dev/v1alpha1]
ClusterTriggerBinding [triggers.tekton.dev/v1beta1]
ClusterInterceptor [triggers.tekton.dev/v1alpha1]

Operator

TektonConfig [operator.tekton.dev/v1alpha1]
TektonInstallerSet [operator.tekton.dev/v1alpha1]
TektonPipeline [operator.tekton.dev/v1alpha1]
TektonTrigger [operator.tekton.dev/v1alpha1]
TektonChain [operator.tekton.dev/v1alpha1]
TektonHub [operator.tekton.dev/v1alpha1]
TektonResult [operator.tekton.dev/v1alpha1]
TektonInstallerSet [operator.tekton.dev/v1alpha1]
OpenShift Pipelines as Code [operator.tekton.dev/v1alpha1]

Advanced APIs

Results

Introduction to API Usage
Results List
Results Details
Result records List
Result logs List
📝 Edit this page on GitHub
Previous PageCore Concepts
Next PageUnderstanding Tekton Hub

#Concepts

#TOC

#Catalog

A catalog is a structured collection of Tekton resources organized according to the Tekton Catalog Organization TEP. Catalogs are the primary source of resources in Tekton Hub.

Tekton Hub supports multiple catalogs, including the official Tekton Catalog and custom catalogs defined by organizations. Each catalog is identified by a unique name and has specific metadata such as organization, type, URL, and revision.

For more information about catalogs and how they work, see Understanding Tekton Hub.

Example of catalog configuration:

catalogs:
- name: tekton
  org: tektoncd
  type: community
  url: https://github.com/tektoncd/catalog
  revision: main

#Resource

A resource is a reusable Tekton component stored in a catalog. Resources can be Tasks, Pipelines, or other building blocks that can be incorporated into CI/CD workflows.

Each resource has metadata such as name, kind, version, description, and tags. Resources are categorized to make them easier to discover and can be rated by users to indicate their quality and usefulness.

For more information about resources and how they're managed, see Understanding Tekton Hub.

Example of a resource in Tekton Hub:

name: git-clone
kind: Task
description: "Clone a git repository into a workspace"
tags: ["git", "clone"]
versions:
  - version: "0.1"
    displayName: "0.1"
    description: "Initial version"
  - version: "0.2"
    displayName: "0.2"
    description: "Added authentication support"

#Category

Categories are classifications used to organize resources by their purpose or functionality. They help users discover relevant resources more easily by grouping similar components together.

Tekton Hub comes with predefined categories, and administrators can add new categories as needed. Each resource can belong to one or more categories.

For more information about how categories help with resource discovery, see Understanding Tekton Hub.

Examples of categories:

  • Build Tools
  • Cloud Providers
  • Deployment
  • Image Build
  • Testing
  • Security

#API Service

The API Service is the backend component of Tekton Hub that provides data access and management functionality. It offers both versioned APIs for external integration and internal APIs for the UI and system operations.

Versioned APIs are stable interfaces with backward compatibility guarantees, while internal APIs may change without notice and are primarily used by the Tekton Hub UI.

For more information about the API Service and its architecture, see Understanding Tekton Hub.

#Catalog Refresh

Catalog refresh is the process by which Tekton Hub updates its database with the latest resources from configured catalogs. This can be triggered manually or scheduled to run at regular intervals.

For more information about catalog refresh, see Understanding Tekton Hub.