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

#Introduction

#TOC

#Overview

Tekton is a powerful and flexible open-source framework for creating CI/CD systems, allowing developers to build, test, and deploy across cloud providers and on-premise systems. As part of the CD Foundation, a Linux Foundation project, Tekton provides a set of Kubernetes custom resources that serve as building blocks for creating cloud-native CI/CD pipelines.

The Alauda DevOps Pipelines Operator provides a simplified way to install, upgrade, and manage the lifecycle of Tekton components on Kubernetes clusters. It extends Kubernetes functionality by installing and managing Tekton Pipelines and its associated components, making it easier to set up and maintain a robust CI/CD environment.

#Key Components

#Alauda DevOps Pipelines Operator

The Alauda DevOps Pipelines Operator is a Kubernetes operator that manages the lifecycle of Tekton components. It provides:

  • Simplified installation and management of Tekton components
  • Automatic upgrades and configuration management
  • Centralized control of Tekton resources across the cluster
  • Custom resource definitions (CRDs) for managing Tekton components

#Tekton Pipelines

Tekton Pipelines is the core component that provides the fundamental building blocks for creating CI/CD workflows. It includes:

  • Tasks: The smallest, atomic units of work that perform specific operations
  • Pipelines: A collection of tasks arranged in a specific order of execution
  • TaskRuns: The execution and status of a task
  • PipelineRuns: The execution and status of a pipeline
  • Workspaces: A mechanism for sharing data between tasks

Tekton Pipelines enables you to define complex workflows as code, making them version-controlled, reusable, and portable across different environments.

#Tekton Triggers

Tekton Triggers extends Tekton Pipelines with event-based capabilities, allowing you to:

  • Listen for external events (webhooks from Git repositories, container registries, etc.)
  • Extract information from these events
  • Create PipelineRuns or TaskRuns based on the event data
  • Pass event data to the created PipelineRuns or TaskRuns

This enables fully automated CI/CD workflows that respond to events such as code commits, pull requests, or image pushes.

#Tekton Chains

Tekton Chains focuses on supply chain security by:

  • Automatically capturing and signing provenance information for all TaskRuns
  • Supporting multiple signature formats and storage backends
  • Providing attestations in industry-standard formats like in-toto
  • Securing the software supply chain from source to deployment

Chains observes TaskRun executions, takes snapshots when they complete, converts them to standard payload formats, signs them, and stores them securely.

#Tekton Results

Tekton Results addresses the challenge of long-term storage and querying of CI/CD execution data by:

  • Separating result storage from the Pipeline controller
  • Providing a queryable API for accessing historical pipeline data
  • Enabling custom metadata for CI/CD workflows
  • Grouping related workloads together
  • Storing logs from TaskRuns and PipelineRuns
  • Freeing up cluster resources by allowing cleanup of completed runs

#Advantages

  • Kubernetes-Native: Built specifically for Kubernetes, leveraging its scaling and management capabilities
  • Declarative: Define your pipelines as code using YAML, enabling version control and automation
  • Modular: Compose complex workflows from reusable components
  • Extensible: Create custom tasks or use community-contributed tasks from the Tekton Hub
  • Vendor-Neutral: Works across different cloud providers and environments
  • Secure: Built-in security features with Tekton Chains for supply chain security

#Use Cases

  • Continuous Integration: Automatically build and test code changes
  • Continuous Delivery: Automate the delivery of applications to various environments
  • GitOps Workflows: Implement GitOps practices for application and infrastructure deployments
  • Secure Software Supply Chain: Ensure the integrity and security of your software from source to deployment
  • Multi-Cloud Deployments: Create consistent CI/CD pipelines across different cloud providers

#Limitations

  • Learning Curve: Requires understanding of Kubernetes concepts and resources
  • Resource Requirements: Needs adequate cluster resources for running pipelines
  • Complexity for Simple Workflows: May be overly complex for very simple CI/CD needs
  • Initial Setup: Requires proper configuration and setup of multiple components

The Alauda DevOps Pipelines Operator simplifies many of these challenges by providing an integrated and managed experience for Tekton on Kubernetes clusters.