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 PageTriggers
Next PageArchitecture

#Introduction

#TOC

#What is Tekton Triggers?

Tekton Triggers is a crucial component of Tekton that allows users to detect and extract event information from various sources, enabling deterministic instantiation and execution of TaskRuns and PipelineRuns based on that information. It is installed as an extension of Tekton Pipelines on a Kubernetes cluster.

#Core Features

  1. Event Listening and Handling

    • Supports multiple event sources (such as GitHub, GitLab, generic Webhooks, etc.)
    • Provides an extensible event handling mechanism
    • Supports event filtering and validation
  2. Resource Instantiation

    • Automatically creates TaskRuns and PipelineRuns
    • Supports dynamic parameter passing
    • Offers templated configuration
  3. Security and Scalability

    • Built-in security mechanisms
    • Supports custom interceptors
    • Provides fine-grained permission control

#How It Works

Tekton Triggers works in conjunction with the following core components:

  1. EventListener

    • Listens on a specified port in the Kubernetes cluster
    • Receives and processes external events
    • Manages trigger configurations
  2. Trigger

    • Defines how to handle received events
    • Specifies bindings and templates
    • Configures interceptors for event validation
  3. TriggerBinding

    • Extracts data from events
    • Maps data to parameters
    • Supports JSONPath expressions
  4. TriggerTemplate

    • Defines the resource templates to be created
    • Uses parameters to dynamically generate resources
    • Supports the creation of multiple resources
  5. Interceptors

    • Validates the authenticity of events
    • Filters and transforms event data
    • Provides extension points

#Use Cases

Tekton Triggers is suitable for the following scenarios:

  1. Continuous Integration/Continuous Deployment (CI/CD)

    • Automatically triggers builds on code commits
    • Triggers tests on merge requests
    • Deploys on release events
  2. Automated Operations

    • Triggers remediation processes for monitoring alerts
    • Initiates maintenance processes for scheduled tasks
    • Scales resources in response to system events
  3. Cross-System Integration

    • Receives events from third-party systems
    • Triggers data synchronization processes
    • Coordinates workflows across multiple systems

#Key Advantages

  1. Flexibility

    • Supports various event sources
    • Customizable handling logic
    • Dynamic resource creation
  2. Scalability

    • Supports custom interceptors
    • Horizontally scalable
    • Cluster-level deployment support
  3. Security

    • Built-in authentication
    • Fine-grained permission controls
    • Event validation mechanisms
  4. Maintainability

    • Declarative configuration
    • Templated management
    • Version control friendly

#Next Steps

  • Quick Start
  • Configuration Guide
  • Learn about Tekton Triggers

#Reference Resources

  • Official Documentation
  • GitHub Repository
  • Example Collection