It is an open-source tool initially developed by Google for internal use, later open-sourced, and widely adopted for building and deploying applications in Kubernetes environments. When deployed in a Kubernetes cluster, Tekton seamlessly integrates with the environment, streamlining the application pipeline delivery process. It automatically triggers when code is merged into the main branch, operating natively within Kubernetes without requiring additional external components. The automated pipeline, initiated by Tekton, builds the application, deploys it to specified container registries, and then to the Kubernetes cluster. Tekton's versatility shines in multi-environment setups like staging, testing, and production, efficiently managing the continuous integration (CI) part by triggering processes linked to code merges. Users often integrate Argo CD to complement Tekton in the continuous deployment (CD) phase. Argo CD pulls and deploys the latest application image within the Kubernetes cluster, creating a comprehensive and automated CI/CD workflow.
Tekton is the orchestration engine within OpenShift, which is our on-premise platform. Since we are not on the cloud yet, OpenShift plays a strategic role, and Tekton is a significant part of it. It serves as an orchestrator. In my experience of the last two years using Tekton and OpenShift pipelines, I haven't encountered many issues. As an orchestrator, Tekton works best. It's just one component of the larger OpenShift platform. Tekton consists of multiple components like events, trigger bindings, and more. However, when it comes to the overall OpenShift platform, being a platform as a service, most aspects are taken care of.
Cloud Architect at a financial services firm with 10,001+ employees
Real User
Top 20
2023-02-10T12:11:36Z
Feb 10, 2023
We are utilizing Tekton as a pipeline tool for their CI/CD process, which involves connecting GitLab to Nexus, then Nexus to Argo CD, and ultimately to Kubernetes.
Tekton is a powerful yet flexible Kubernetes-native open-source framework for creating 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.
It is an open-source tool initially developed by Google for internal use, later open-sourced, and widely adopted for building and deploying applications in Kubernetes environments. When deployed in a Kubernetes cluster, Tekton seamlessly integrates with the environment, streamlining the application pipeline delivery process. It automatically triggers when code is merged into the main branch, operating natively within Kubernetes without requiring additional external components. The automated pipeline, initiated by Tekton, builds the application, deploys it to specified container registries, and then to the Kubernetes cluster. Tekton's versatility shines in multi-environment setups like staging, testing, and production, efficiently managing the continuous integration (CI) part by triggering processes linked to code merges. Users often integrate Argo CD to complement Tekton in the continuous deployment (CD) phase. Argo CD pulls and deploys the latest application image within the Kubernetes cluster, creating a comprehensive and automated CI/CD workflow.
Tekton is the orchestration engine within OpenShift, which is our on-premise platform. Since we are not on the cloud yet, OpenShift plays a strategic role, and Tekton is a significant part of it. It serves as an orchestrator. In my experience of the last two years using Tekton and OpenShift pipelines, I haven't encountered many issues. As an orchestrator, Tekton works best. It's just one component of the larger OpenShift platform. Tekton consists of multiple components like events, trigger bindings, and more. However, when it comes to the overall OpenShift platform, being a platform as a service, most aspects are taken care of.
We are utilizing Tekton as a pipeline tool for their CI/CD process, which involves connecting GitLab to Nexus, then Nexus to Argo CD, and ultimately to Kubernetes.