Harness Reviews

We use Harness as a deployment tool. It allows us to define environments like OpenShift or Kubernetes or Linux servers. 

It automates the pipeline system where users can trigger with the master branch. We use Tekton to run without any manual interaction. Once the build is done, it stores artifacts in JFrog, and Harness detects them automatically and executes deployment.

Harness has been much faster and user-friendly for the end user for deployment purposes. It allows us to do changes in the build stage during deployment, making processes more efficient. 

Harness also allows for modifications at the YAML level, which is beneficial for our pipeline and deployment processes.

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

It facilitates deployment by allowing a user to push their code into GitHub or Bitbucket and have it deployed without manual management intervention.

Even with automation, there's a requirement for manual change requests for approvals. If this is corrected, we could have a totally automated pipeline. Otherwise, we need to use GitLab or GitOps to trigger automatically with every commit.

I have been working with Harness for four to five months.

Harness is stable. There is no high latency or deployment delay, and it has proven to be reliable.

Currently, we are scaling up the pipelines with Harness, which provides functionality to achieve this without any significant issues.

There is a dedicated team within the organization to handle incidents and issues with Harness, so we don't need to rely on external support much.

We were previously using a different tool for deployments which had its limitations. Now, we use Tekton for continuous integration and Harness for deployment.

There were no significant challenges with the initial setup. We had a dedicated team for the implementation and were able to get support when needed.

For the implementation, there was a dedicated team handling Harness, which made the process streamlined.

Harness offers a user-friendly deployment experience with faster processes compared to the previous tools we were using.

I do not have information on the pricing, setup cost, and licensing as I am working for a client, and it is handled at the organizational level.

We have evaluated Jenkins and Tekton for continuous integration, yet Harness is used for deployment.

I recommend Harness to other users. As part of the engineering team, my role includes certifying products for applications, and Harness has proven suitable for our needs. I suggest adopting it based on usage requirements.

I'd rate the solution eight out of ten.

We use Harness for deploying Kubernetes clusters. It is a SaaS-based tool with a good graphical user interface. We can create workflows and deployment pipelines and easily visualize them. We can see the logs and understand where the pipeline is breaking. It's a highly customizable DevOps tool.

The platform's most valuable features are ease of use and a good graphical user interface.

The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the tool. There's also room for improvement in debugging pipeline issues, which can sometimes become complex. Limitations regarding reconciliation features and support for certain parts of the infrastructure should also be addressed.

The product is stable.

We have five Harness users in our organization. Being a SaaS product, scalability should not be an issue.

The decision to use Harness was primarily driven by its secure support for Kubernetes services and user-friendly deployment process, which requires minimal knowledge. The company sought to simplify and reduce the complexity and risks associated with deployment processes. Opting for a SaaS solution allowed them to avoid managing infrastructure and pay on a per-usage basis, providing scalability without the burden of infrastructure management. Additionally, Harness offers features such as log collection, integration with cloud storage services like S3, and auto-healing capabilities.

The pricing aspect needs to be considered first based on your requirements. Secondly, it might be suitable if your team is technically proficient in tools like Argo CD. However, if you have a complex infrastructure and limited personnel to manage it, Harness would be a better choice.

We integrated Harness with Kubernetes, and the setup didn't significantly affect our existing infrastructure. Learning to use Harness for basic tasks is relatively easy, but mastering complex operations may require time and team support.

I rate it a seven out of ten.