Harness vs Tekton comparison

"Harness starts integrating with organizations, making everything automated without the need for manual interruption."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."

"It's a highly customizable DevOps tool."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."

"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."

"Tekton is serverless and runs on OpenShift, and we leverage Tekton to take full advantage of the Kubernetes features such as running and scaling the solution in PaaS."

"The ability to scale is valuable."

"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."

"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."

"The installation process is seamless, requiring fewer resources compared to Jenkins."

"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."

"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."

"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."

"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

"Even with automation, there's a requirement for manual change requests for approvals."

"I prefer the previous less compact UI version of Harness, which showed more details on the screen."

"Tekton should include many features to integrate event-driven pipelines."

"RBAC is really needed for Tekton."

"When we started with Tekton around 2021 or early 2022, the community support was somewhat limited, which posed challenges when dealing with issues or debugging. We had to rely on Red Hat OpenShift support to overcome these challenges. However, I believe that these issues will naturally improve over timeas the developer community grows stronger. From a technical perspective, I haven't had the opportunity to deeply evaluate the product end-to-end, especially in the past year or so, when I've been less involved with it."

"Tekton is a good product with all the features I need. There isn't anything that needs improvement."

"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."

"While Tekton is highly effective for Kubernetes-based setups, it might not suit users who require more control over bare-metal environments."

"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."

"The product's scalability can be challenging when multiple users access it simultaneously."

"It is entirely open source and free of charge."

"The product is free of cost."

"The product is free and open-source."

"The solution is open-source."

"Tekton is an open-source tool."

"The tool is open-source and free to use."