Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now

Introduction of Tekton

What is Tekton?

Tekton is an open-source cloud-native framework for building continuous integration and delivery (CI/CD) systems. It lets you build, test, and deploy across multiple cloud providers or on-premises systems by abstracting away the underlying implementation details.

Tekton is based on Kubernetes, which makes it easy to use and integrate with other Kubernetes-based tools and services. Tekton also provides a number of features that make it ideal for building CI/CD systems, such as:

  • Declarative approach: Tekton uses a declarative approach to define pipelines, which makes it easy to automate and manage the build process.
  • Flexibility: Tekton is highly flexible and can be used to build CI/CD systems for a wide variety of applications.
  • Extensibility: Tekton is extensible and can be integrated with other tools and services to meet the specific needs of your team.

Tekton is a powerful tool for automating the build, test, and deploy lifecycle of cloud-native applications. It is easy to use, flexible, and extensible, making it a good choice for teams of all sizes.

Terminology used in tekton

Tekton is an open-source platform for building, testing, and deploying cloud-native applications. It uses a declarative approach to define pipelines, which makes it easy to automate and manage the build process.

Here is a list of some of the key terminology used in Tekton:

  • Pipeline: A Pipeline is a set of Tasks that are executed in order to build, test, and deploy an application.
  • Task: A Task is a unit of work that is executed in a Pipeline. Tasks can be used to perform a variety of tasks, such as building a Docker image, running a test suite, or deploying an application to a Kubernetes cluster.
  • PipelineResource: A PipelineResource is a resource that is used by Tasks. PipelineResources can be used to represent a variety of resources, such as source code, Docker images, and Kubernetes manifests.
  • PipelineRun: A PipelineRun is an instance of a Pipeline. PipelineRuns are used to start and manage the execution of Pipelines.
  • Trigger: A Trigger is a service that watches for events and starts PipelineRuns when those events occur. For example, a Trigger could be used to start a PipelineRun when a new commit is pushed to a Git repository.

In addition to these core concepts, Tekton also includes a number of other features, such as:

  • Workspaces: Workspaces are used to provide Tasks with access to the resources they need to execute.
  • Params: Params are used to pass data between Tasks.
  • Results: Results are used to collect and store the output of Tasks.
  • Conditions: Conditions can be used to control the flow of execution within a Pipeline.
  • Pipelines: Pipelines can be chained together to create complex build and deployment workflows.

Tekton will then execute the pipeline steps and build and deploy your application.

Here are some additional tips for configuring Tekton projects:

  • Use Tekton Pipelines to automate the entire build, deploy, and test lifecycle of your applications.
  • Use Tekton Tasks to define the individual steps that will be executed in your pipeline.
  • Use Tekton PipelineResources to represent the inputs and outputs of your pipeline steps.
  • Use Tekton PipelineRuns to start and manage the execution of your pipelines.
  • Use Tekton Triggers to automatically start pipelines when certain events occur, such as a new commit being pushed to a Git repository.

Tekton is a powerful tool for automating the build, deploy, and test lifecycle of your applications. By following the tips above, you can configure Tekton projects to meet the specific needs of your team.

Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x