Tekton Becomes CNCF Incubating: What It Means

Tekton’s move to CNCF Incubation at KubeCon EU 2026 validates what many platform teams already knew: Kubernetes-native CI/CD is the future.

Why This Matters

Tekton is not just another CI/CD tool. It is a Kubernetes-native workflow engine with composable primitives (Steps, Tasks, Pipelines) that run as pods. This means:

• No external CI server — your cluster IS the CI server
• Scalability — pipelines scale with your cluster
• Security — pod security policies, RBAC, and network policies apply to CI/CD
• Portability — pipelines run on any Kubernetes cluster

The Supply Chain Security Story

Tekton’s integration with the CNCF and OpenSSF ecosystem creates a complete supply chain:

1. Tekton — builds and tests code
2. Sigstore (OpenSSF) — signs artifacts cryptographically
3. ArgoCD (CNCF) — deploys signed artifacts via GitOps
4. SPIFFE/SPIRE (CNCF) — provides workload identity

No other CI/CD tool has this depth of cloud native integration.

Who Uses Tekton

• Red Hat OpenShift Pipelines — Tekton is the CI/CD engine
• IBM Cloud Continuous Delivery — built on Tekton
• Puppet — uses Tekton for delivery pipelines
• Ford Motor Company — enterprise adoption

Tekton vs Other CI/CD Options

For a detailed comparison, see Tekton vs GitHub Actions and GitLab CI Tutorial.

My Prediction

Tekton’s CNCF Incubation accelerates enterprise adoption. The combination of Kubernetes-native execution, supply chain security, and integration with ArgoCD and Sigstore makes it the most secure CI/CD option for cloud native teams.

If you run Jenkins or external CI/CD and want to move security closer to your workloads, Tekton is the path forward.

Related Resources

• Tekton vs GitHub Actions
• GitHub Actions CI/CD Tutorial
• GitLab CI Tutorial
• ArgoCD Cheat Sheet
• DevSecOps Pipeline
• Jenkins vs GitHub Actions

About the Author

I am Luca Berton, AI and Cloud Advisor. I design CI/CD pipelines for enterprise Kubernetes platforms. Book a consultation.