Pipelines run on-demand in isolated containers ● No central server to maintain! No plugin conflicts! ● Task library and integration with Tekton Hub ● Secure pipelines aligned with Kubernetes RBAC ● Visual OperatorHub ● CLI, Web, VS Code and IntelliJ plugins OPENSHIFT PIPELINES 21 Task step step Task step Task step step Task step step Pipeline OPENSHIFT PIPELINES Tekton Concepts step Tekton script:|- #!/usr/bin/env python3 ... OPENSHIFT PIPELINES Tekton Concepts: Task 23 OPENSHIFT PIPELINES kind: Task metadata: name: buildah spec: params: - name: IMAGE steps: - name: build

serviceaccount.yaml ├── 03-tasks │ ├── buildah-task.yaml │ ├── create-github-status-task.yaml │ ├── deploy-from-source-task.yaml │ └── deploy-using-kubectl-task.yaml ├── 04-templatesandbindings │ ├── (9+ months) ECOSYSTEM UX ` CORE UX ● Unprivileged pipelines ● Auto-pruning pipeline runs and task runs ● Pipeline admin metrics in Prometheus ● In-cluster Tekton catalog and hub ● Jenkins migration official Tekton catalogs ● App Services (MW) Tasks ● Community-contributions ● OCI artifacts for task distribution ● Additional Tekton resource types in Hub CORE ● Console pages for all Tekton resources

changes automatically. Without GitOps, reverting to a previous configuration state is a complicated task that becomes nearly impossible if the changes are not properly documented. Streamlined, automated automated pipeline. This declarative version-controlled approach makes the time- consuming, daunting task of managing infrastructure painless while increasing the visibility, reliability, and stability of

breaking down monolithic applications into microservices, which can be a complex and resource-intensive task - but one that will pay off by providing flexibility in the future. Another significant challenge

Requests on its own in an unattended manner. Automating Pull Requests might sound like an easy task, but in order to give plenty of visibility on what is happening at any point in time, we need a

or many clusters, each one running a PipeCD agent. This control plane is state- less. Its central task is to manage deployments on other clusters running the PipeCD agents. The control plane manages authentication