Tekton Joins the CNCF as an Incubating Project After Seven Years of Kubernetes-Native CI/CD Development
The CNCF Technical Oversight Committee has voted to accept Tekton, the Kubernetes-native CI/CD framework with 600-plus contributors and 11,000 GitHub stars, ending its tenure as a CD Foundation graduated project.
Overview
The Cloud Native Computing Foundation has accepted Tekton as an incubating project, placing Kubernetes’ most widely deployed CI/CD framework under the same organizational umbrella as Kubernetes itself. The CNCF Technical Oversight Committee voted to approve the move on March 24, completing a transition that ends Tekton’s seven-year tenure at the Continuous Delivery Foundation.
Tekton enters the CNCF with more than 600 contributors, 11,000 GitHub stars, over 5,000 merged pull requests, and a stable v1.0 release for its core Pipelines component, according to the CNCF announcement. The project powers commercial CI/CD offerings including Red Hat OpenShift Pipelines and IBM Cloud Continuous Delivery, and runs in production at organizations such as Ford Motor Company, Puppet, and Nubank.
What We Know
Tekton originated as the build component of Knative, Google’s serverless platform for Kubernetes, before being spun out as an independent project and donated to the newly created Continuous Delivery Foundation in March 2019. The CDF was established as a Linux Foundation initiative with four founding projects: Jenkins, Jenkins X, Spinnaker, and Tekton.
During its time at the CDF, Tekton achieved graduated status — the foundation’s highest maturity level — and developed a governance model that caps any single company’s representation at 40 percent of governing board seats. Its Tekton Enhancement Proposals require approval from maintainers at a minimum of two different companies, according to details in the CNCF incubation application.
The CD Foundation framed the departure as a natural progression rather than a loss. Tekton “arrived as a young project and leaves as a mature, battle-tested framework” that helped define what Kubernetes-native CI/CD looks like for the industry, according to the CD Foundation announcement. The foundation credited its role in fostering cross-project collaboration that led to initiatives like CDEvents and Shipwright.
“Moving to the CNCF places Tekton alongside other foundational cloud-native projects like Kubernetes, Knative, and Argo,” the Tekton project blog noted. The project now integrates deeply with several CNCF-hosted tools, including Argo CD for GitOps workflows, SPIFFE and SPIRE for workload identity, and Sigstore for artifact signing and verification.
Technical Architecture
Tekton uses composable Kubernetes-native primitives — Steps, Tasks, and Pipelines — to orchestrate sequential or parallel workloads. Unlike CI/CD systems that run as centralized servers, Tekton treats pipeline runs as standard Kubernetes resources, which means they benefit from the same scheduling, scaling, and isolation mechanisms that govern other cluster workloads.
The framework comprises five core components: Pipelines for workflow definition, Triggers for event-based pipeline instantiation, a CLI and Dashboard for operator interfaces, and Chains for supply chain security through artifact signing and attestation. The Chains component is particularly significant as organizations face increasing pressure to produce software bills of materials and comply with SLSA supply chain security standards, as described in the CNCF blog post.
What We Don’t Know
The CNCF accepted Tekton at the incubating tier rather than graduated, despite the project already holding graduated status at the CDF. The CNCF’s graduation criteria differ from the CDF’s, and it remains to be seen how quickly Tekton will pursue CNCF graduation.
The long-term trajectory of the CD Foundation itself is also uncertain. With Tekton’s departure, the foundation’s remaining marquee projects are Jenkins, Spinnaker, and CDEvents. Whether the CDF will attract new flagship projects or consider consolidation with other Linux Foundation initiatives has not been addressed publicly.
For existing users and contributors, both the CNCF and the Tekton project emphasized continuity: APIs, releases, support policies, and contribution workflows remain unchanged. Infrastructure and process alignment with CNCF standards will take place gradually over the coming months.
Analysis
The move reflects a broader pattern of consolidation in cloud-native governance. As Kubernetes has become the de facto standard for container orchestration, projects that orbit the Kubernetes ecosystem increasingly gravitate toward the CNCF, where shared infrastructure, cross-project collaboration, and a unified vendor-neutral governance model reduce friction. Tekton’s presence alongside Argo CD, Flux, and other delivery-focused CNCF projects creates a more cohesive CI/CD landscape within a single foundation.
The transition also underscores how the CI/CD market has evolved since 2019. When the CDF was founded, Kubernetes-native pipelines were still emerging alongside traditional Jenkins-style automation. Today, Tekton’s composable primitives have become foundational plumbing for an entire generation of deployment tools, making its alignment with the CNCF both organizationally and technically logical.
Tekton’s roadmap priorities — SLSA Level 3 compliance, Trusted Artifacts for secure inter-task data sharing, improved developer syntax, and enhanced scheduling via Kueue — suggest the project’s next phase will focus on tightening supply chain security and reducing the complexity that has historically been a barrier to direct adoption, according to the CNCF announcement.