What advice do you have for others considering Tekton?

I am preparing documentation to compare Tekton and Jenkins for a new project. The goal is to highlight Tekton's benefits and potentially advocate for its adoption. I'd rate the solution ten out of ten.

I would recommend Tekton to my coworkers if they use Kubernetes most at work. However, if my colleagues don't use Kubernetes, I wouldn't recommend Tekton to them because it is very difficult to understand Tekton if you aren't familiar with Kubernetes. I'd rate the solution eight out of ten.

I recommend Tekton, but users should have some underlying knowledge about how CI/CD pipelines work. I'd rate the solution eight out of ten.

Tekton was initially very daunting, and it took me a long time to get the flow. However, once you get it, it’s awesome. I'd rate the solution six out of ten.

I recommend Tekton for CI/CD pipelines due to its event-driven capabilities and Kubernetes-native approach. The setup, maintenance, and cost benefits are significant. Tekton's approach to managing pipelines as code ensures that you can easily recreate and maintain your pipelines across any supported infrastructure. I'd rate the solution six out of ten.

Tekton has been more than other solutions efficient as it reduces the need to maintain servers like Jenkins. Overall, I rate it a nine out of ten.

Overall, I would rate it a nine out of ten. Once you are used to it, it is a very user-friendly application. Tekton is a great application that simplifies deployments, and customers are happy once their application is up and running, whether through a website or another method. So, it's highly available. If there are any issues, we can now easily deploy continuous updates, and it won't disrupt the application.

I suggest utilizing available tasks and resources, such as copying and using tools like ChatGPT, to write and configure tasks. The platform is user-friendly and provides good support for managing different pipelines. I rate it an eight out of ten.

Tekton's integration capabilities have helped our company's development workflow. Tekton is a Kubernetes native framework, so most of the command lines that we use in Kubernetes could also be used within Tekton framework. Basically, configuring Tekton Pipelines within our Kubernetes cluster was very easy compared to using other solutions. Overall, the development workflow was easy when using Tekton. As a beginner who is trying to use Tekton, it will take some effort to learn it because the documentation in Tekton has to improve a lot. There are no tutorials to learn about Tekton because I personally learned it from my seniors and my experience and even when we faced challenges in the development, we couldn't find a solution on the internet. We had to do our own trial and error to find a solution, which was one of the main challenges while using Tekton. I recommend the tool to others as using Tekton makes our lives easier. As far as I know, many companies don't know about Tekton. If they knew that there is something called Tekton, they would definitely adjust to it. I rate the tool a nine out of ten.

Overall, I would rate the solution a seven out of ten because there are lots of areas for improvement. I would recommend it to someone who is well-versed in Kubernetes and can debug internal issues, not to any newcomers. I would suggest they explore traditional legacy tools first.

I wouldn't recommend the product to others. I recommend GitLab for anyone looking to work on mature CI/CD pipelines. I rate the overall product a four out of ten.

Tekton integrates seamlessly with GitHub, creating three distinct environments: pre-production, development, and testing. Each environment is efficiently managed using Spectrum. It maintains its variables and comments before launching pipelines in any environment, ensuring clear separation. Installing it on OpenShift is considered one of the most valuable tools for DevOps engineers, providing a comprehensive view of the application. Tekton was utilized within OpenShift and deployed on an on-premise server. We employed Argo CD for deployment. Kubernetes manifests were authorized and stored in GitHub. Tekton is tailored for the GitOps approach and is recommended to be integrated directly with GitHub repositories. With Tekton, CI pipelines were initiated. After completing the CI process, an image was generated and stored in GitHub. Subsequently, this image was utilized by Argo CD as a container for deployment, and OpenShift deployed it using Kubernetes manifests. I recommend Tekton to my friends who work on a per-shift basis instead of Jenkins because, with Tekton, you don't need to install plugins or configure them. All the necessary plugins are already installed in the base image of the tool you want to use. You must install that base image, which is readily available in the developer hub or from another image provider. Tekton is easy to use in the pharmaceutical industry. This ease of use stems from its versatility in supporting two main types of workflows: working with AML files or utilizing forms with cases to manage and specify parameters and comments. We are an organization focused on automating infrastructure and creating CI/CD pipelines for application development. My advice is to leave it for open source rather than having the technical enterprise handle it, allowing students and universities to engage with it. As an instructor, It is advantageous for them to learn and adopt Tekton because it's relatively easy compared to Jenkins. Many students and Jenkins users struggle to learn about CI/CD and default pipelines, so I strongly recommend using Tekton. Overall, I rate the solution a nine out of ten.

I highly recommend that you operate in a Kubernetes-based environment closely integrated with Kubernetes. However, I suggest deploying it in a separate cluster, not where your primary workloads run, to avoid potential disruptions to production cluster resources. I also recommend it for users who are already familiar with the tool. While it offers significant capabilities, harnessing its full potential requires a certain level of understanding. Overall, I would rate it seven out of ten.

I would recommend Tekton as an orchestrator because it works well within the OpenShift environment. While there may be similar orchestrator components offered by other vendors in different DevOps architectures, Tekton's integration with other OpenShift components makes it a strong choice. I would rate Tekton a seven. The only drawback I've experienced is the difficulty of modifying YAML files on the fly and making changes, as it doesn't work well in that aspect. However, apart from that, Tekton performs well in other areas.

I give the solution a five out of ten. We have around 50 people using the solution in our organization. From a usage perspective, people are trying to move up from Tekton to GitLab in our organization. Using Tekton depends on the strength of our Red Hat resources. I recommend GitLab over Tekton.