It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges. This aspect could be enhanced for better efficiency. Additionally, the build time, particularly for larger applications, seems a bit extended, ranging from five to ten minutes in some cases. There's room for improvement to streamline and minimize the build time.
There might be occasional issues with storage or cluster-level logging, which can affect production. But as a component, Tekton performs flawlessly. As an orchestrator, Tekton effectively executes most tasks. However, there are instances where we feel that YAML files, which Tekton reads, could benefit from increased flexibility. You see, in OpenShift, everything revolves around YAML. We have different components specified in YAML files, and when we put them together in an OpenShift pipeline, it generally works fine. However, occasionally we encounter difficulties when editing these YAML files.
Cloud Architect at a financial services firm with 10,001+ employees
Real User
Top 20
2023-02-10T12:11:36Z
Feb 10, 2023
There is a need for substantial improvement in connecting with other tools and open-source software. Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers. Furthermore, there is no existing template that gives defaults for developers to build a pipeline, making it challenging for them to use. In conclusion, Tekton is not particularly user-friendly for developers and has room for improvement. I would like Tekton to change its dashboard to be similar to the one GitLab offers.
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 tends to occupy a significant amount of disk space on the node, which could potentially pose challenges. This aspect could be enhanced for better efficiency. Additionally, the build time, particularly for larger applications, seems a bit extended, ranging from five to ten minutes in some cases. There's room for improvement to streamline and minimize the build time.
There might be occasional issues with storage or cluster-level logging, which can affect production. But as a component, Tekton performs flawlessly. As an orchestrator, Tekton effectively executes most tasks. However, there are instances where we feel that YAML files, which Tekton reads, could benefit from increased flexibility. You see, in OpenShift, everything revolves around YAML. We have different components specified in YAML files, and when we put them together in an OpenShift pipeline, it generally works fine. However, occasionally we encounter difficulties when editing these YAML files.
There is a need for substantial improvement in connecting with other tools and open-source software. Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers. Furthermore, there is no existing template that gives defaults for developers to build a pipeline, making it challenging for them to use. In conclusion, Tekton is not particularly user-friendly for developers and has room for improvement. I would like Tekton to change its dashboard to be similar to the one GitLab offers.