Harness Continuous Delivery Q3 Updates

We’re excited to share the latest updates to the Harness Continuous Delivery (CD) & GitOps module. These enhancements are designed to improve flexibility, streamline configuration, and make advanced deployment strategies more accessible to teams. Here are highlights of what’s new in last quarter. 

Native Support for Helm Deployments to Kubernetes

Historically, our support for Helm deployments covered only the basics, focusing on straightforward deployment patterns. With this update, we’ve elevated Helm deployment capabilities to make it easier than ever to incorporate advanced deployment strategies.

• Enhanced Deployment Strategies: Blue-green and Canary deployments are now as easy as a checkbox. Instead of complex configurations, you can set up these strategies quickly, which simplifies testing and rollout to production.
• Out-of-the-Box Rollbacks: Alongside these strategies, we’ve matched rollback patterns to help you recover seamlessly if an issue arises. With these additions, you can apply the same ease and consistency to your rollbacks as your deployments.

These updates empower you to deliver with confidence, knowing that sophisticated Helm deployment strategies are straightforward and ready to go. Check out the updated docs.

GitOps Enhancements

GitOps continues to be a major focus, and this quarter we’re rolling out many updates to strengthen our GitOps offering. 

• Scalability: Harness has made significant investments in the scalability, security, and resiliency of our GitOps agents and added many features that improve the quality of life for teams managing fleets of GitOps clusters.
• Agent Management: To make it easier to install agents at scale, we have updated our Terraform provider to install GitOps agents. GitOps agents now also support HPA. 
• Label Based RBAC: Access control can be tricky for GitOps. Without a management layer like Harness, teams have to log into each Argo or Flux controller to set permissions. Harness is continuing to make RBAC management easy by centralizing setting up Application level RBAC  in Harness.
• Multiple Source Support: If your Application's resource YAML files are scattered across several repositories, you can now point Harness to those multiple repos and it will act on them together.

These additions to GitOps support your team in maintaining reliable, source-driven operations across multiple environments and clusters.

Additional Updates

Aside from these major highlights, we’ve introduced several smaller but impactful updates this quarter:

1. Triggers: Improvements to triggers, with an emphasis on execution flexibility and performance tuning as well as visibility into trigger events to help with configuration and debugging. 
2. Multi-runtime Support in Serverless: Multiple runtimes are simultaneously supported for deployments to AWS SAM and Serverless. This will simplify configuration for teams using these platforms. 
3. Harness Native Approval: Harness approvals have been enhanced with the ability to define certain allowed values for approval input fields and support for using the Approvals API with service account authentication.  
4. File Uploads: Users can now upload a file from their machine as part of runtime input. For example, manual test results could be uploaded to support approval processes. 
5. Delegate on Read-Only K8s: The Harness delegate may now be installed on Kubernetes where the root file system is read-only. 

For a full list of updates and detailed documentation, check out the release notes.

This quarter’s enhancements reflect our ongoing commitment to simplifying deployment workflows while providing engineers and DevOps teams with the control and flexibility they need. As always, we’re looking forward to your feedback as we continue to evolve the Harness CD & GitOps module to better support your goals.

‍