OpenShift Pipelines are based on Tekton, an open-source framework for building Continuous Integration/Continuous Deployment (CI/CD) pipelines natively in Kubernetes.
Tekton provides Kubernetes-native CI/CD functionality by defining pipeline resources as custom resources (CRDs) in OpenShift. This allows for scalable, cloud-native automation of software delivery.
Kubernetes-Native: Unlike Jenkins, which requires external servers or agents, Tekton runs natively in OpenShift/Kubernetes.
Serverless & Declarative: Pipelines are defined using YAML configurations, and execution is event-driven.
Reusable & Extensible: Developers can define Tasks, Pipelines, and Workspaces to create modular workflows.
Integration with GitOps: OpenShift Pipelines support Argo CD for GitOps-based deployment strategies.
Why Tekton is Used in OpenShift Pipelines?Example of a Tekton Pipeline Definition in OpenShift:apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
name: example-pipeline
spec:
tasks:
- name: echo-hello
taskSpec:
steps:
- name: echo
image: ubuntu
script: |
#!/bin/sh
echo "Hello, OpenShift Pipelines!"
A. Travis → ❌ Incorrect
Travis CI is a cloud-based CI/CD service primarily used for GitHub projects, but it is not used in OpenShift Pipelines.
B. Jenkins → ❌ Incorrect
OpenShift previously supported Jenkins-based CI/CD, but OpenShift Pipelines (Tekton) is now the recommended Kubernetes-native alternative.
Jenkins requires additional agents and servers, whereas Tekton runs serverless in OpenShift.
D. Argo CD → ❌ Incorrect
Argo CD is used for GitOps-based deployments, but it is not the underlying technology of OpenShift Pipelines.
Tekton and Argo CD can work together, but Argo CD alone does not handle CI/CD pipelines.
Explanation of Incorrect Answers:
IBM Cloud Pak for Integration CI/CD Pipelines
Red Hat OpenShift Pipelines (Tekton)
Tekton Pipelines Documentation
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
Submit