October 10, 2019 By Steven Weaver 2 min read

What is Tekton?

What if you were able to build, test, and deploy apps to Kubernetes using an open source, vendor-neutral, Kubernetes-native framework?

That’s the promise of Tekton, a set of shared components for building continuous integration and continuous delivery (CI/CD) systems, managed by the open source Continuous Delivery Foundation (CDF). 

The goal is to modernize continuous delivery by providing industry specifications for pipelines, workflows, and other building blocks. Tekton lets you build, test, and deploy across multiple cloud providers or on-premises systems by abstracting the underlying implementation details.

How does Tekton work?

Simply put, the Tekton Pipelines project provides Kubernetes-style resources for declaring CI/CD-style pipelines. These resources are naturally described in yaml and stored in a code repository. This pipeline-as-code approach provides the benefits of versioning and source control.   

Tekton provides a set of Custom Resource extensions to Kubernetes that define pipelines and related concepts. The following are the basic Tekton Pipeline building blocks:

  • Task: Defines a set of build steps, such as compiling code, running tests, and building and deploying images.
  • Pipeline: Defines the set of tasks that compose a pipeline.
  • PipelineResource: Defines an object that is an input (such as a Git repository) or an output (such as a Docker image) of the pipeline.
  • PipelineRun: Defines the execution of a pipeline. This resource references the Pipeline to run and which PipelineResource(s) to use as input and output.

Apart from being Kubernetes-native, a Tekton pipeline can be used to deploy to any environment (Kubernetes cluster, Cloud Foundry, virtual machines (VMs), etc.) and pipeline tasks are run securely in isolation, together providing the ability to flexibly meet the needs of modern continuous delivery.

IBM is committed to providing continuous delivery tools based on Tekton and, earlier this year, announced the first Tekton-based capability with private pipeline workers, allowing the ability to run Continuous Delivery Pipeline stages outside of the IBM public infrastructure. Stay tuned for additional Tekton features coming soon! 

For a closer look, see our video, “What is Tekton?”:

The Continuous Delivery Foundation

The Continuous Delivery Foundation (CDF) serves as the vendor-neutral home of many of the fastest-growing projects for continuous delivery, including Jenkins, Jenkins X, Spinnaker, and Tekton. CDF supports DevOps practitioners with an open model, training, industry guidelines, and a portability focus.

IBM is a premier sponsor of the CDF and is actively participating in this community and its ecosystem to help shape the future of CI/CD. Our participation in this foundation ensures that we can offer our customers leading-edge, cloud native solutions that deliver high-quality applications with speed.

Contact

If you have questions, engage our team via Slack by registering here and join the discussion in the #ask-your-question channel on our public Cloud DevOps @ IBM Slack

We’d love to hear your feedback.

More from Cloud

Get ready for change with IBM Cloud Training

2 min read - As generative AI creates new opportunities and transforms cloud operations, it is crucial to learn how to maximize the value of these tools. A recent report from the IBM Institute for Business Value found that 68% of hybrid cloud users already have a formal, organization-wide policy or approach for the use of generative AI. That same report also noted that 58% of global decision makers say that cloud skills remain a considerable challenge. Being proactive in your learning can significantly…

Data center consolidation: Strategy and best practices

7 min read - The modern pace of data creation is staggering. The average organization produces data constantly—perhaps even continuously—and soon it’s investing in servers to provide ample storage for that information. In time, and probably sooner than expected, the organization accrues more data and outgrows that server, so it invests in multiple servers. Or that company could tie into a data center, which is built to accommodate even larger warehouses of information. But the creation of new data never slows for long. And…

Hybrid cloud examples, applications and use cases

7 min read - To keep pace with the dynamic environment of digitally-driven business, organizations continue to embrace hybrid cloud, which combines and unifies public cloud, private cloud and on-premises infrastructure, while providing orchestration, management and application portability across all three. According to the IBM Transformation Index: State of Cloud, a 2022 survey commissioned by IBM and conducted by an independent research firm, more than 77% of business and IT professionals say they have adopted a hybrid cloud approach. By creating an agile, flexible and…

Tokens and login sessions in IBM Cloud

9 min read - IBM Cloud authentication and authorization relies on the industry-standard protocol OAuth 2.0. You can read more about OAuth 2.0 in RFC 6749—The OAuth 2.0 Authorization Framework. Like most adopters of OAuth 2.0, IBM has also extended some of OAuth 2.0 functionality to meet the requirements of IBM Cloud and its customers. Access and refresh tokens As specified in RFC 6749, applications are getting an access token to represent the identity that has been authenticated and its permissions. Additionally, in IBM…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters