Q3 FY27 Product Update: Harness GitOps | Harness Blog

Welcome to the first dedicated GitOps edition of our quarterly update series! Until now, GitOps updates were shared in a post with Continuous Delivery, where Q1 brought AI-powered operations, centralized notifications, and PR workflow improvements, and Q2 added application rollback, applications in any namespace, and finer-grained RBAC. Q3 FY27 builds on these foundations with post-production rollback from the Services dashboard, new Update Release Repo capabilities for PR pipelines, Argo CD import history, agent metrics, and Argo CD 3.5, giving you more control over how changes flow from Git to production.

Applications and Deployments

More control over how applications are deployed, rolled back, and seen by the people who use them.

Post-production rollback for applications

Roll back a GitOps application from the Services dashboard after a successful pipeline deployment, using the same stage configuration as the original deploy. Requires Execute permission on the original pipeline and enablement through Harness Support.
Learn more

Service instance details after syncs

GitOps services now show instance details and deployment state based on sync operations, even when applications sync outside a pipeline. Link applications to a service and environment with the harness.io/serviceRef and harness.io/envRef labels. Enabled through Harness Support.
Learn more

Choose steps for a new GitOps CD stage

Choose which steps to add when you first create a GitOps CD stage, with Single App, App Set, or Rollout strategies, instead of a fixed set.
Learn more

Success Criteria for Sync and Rollback steps

GitOps Sync and Rollback steps now support a Success Criteria setting. Sync Succeeded (the default) passes once Argo CD reports the sync complete, while Sync Initiated passes as soon as Argo CD accepts the request, which suits Argo Rollouts awaiting manual promotion. Sync Initiated cannot be combined with Wait until healthy, Show Resource Progress, or Select Promote Option for Rollouts.
Learn more

App of Apps tab

A dedicated App of Apps tab in the GitOps UI lets you manage parent and child applications in one place. Use it to view and act on a parent application together with its children rather than one by one.
Learn more

Per-application RBAC filtering always on

The application list and dashboard overview now always show only the applications a user is authorized to see, based on the resource groups and application labels in your RBAC setup.
Learn more

PR Pipelines

More visibility, cleaner repositories, and finer control in the Update Release Repo, Revert PR, and Merge PR steps.

GitHub status checks for Update Release Repo

Update Release Repo posts status checks to the pull request it creates: one when the PR is created and one reporting the stage result when the stage completes. Requires delegate 26.08.89900 or later.
Learn more

Automatic branch cleanup

The Update Release Repo step now deletes its temporary branches after both successful and failed runs, so stale branches do not pile up in your repository. Cleanup is automatic, with no extra step or script needed. Learn more

Pattern-based File Path matching

One service can update multiple files and raise a single PR using path patterns: * within a path segment, ** across nested folders, and ! to exclude. Patterns support <+cluster.name>, <+env.name>, and <+envgroup.name>, and match only .yaml, .yml, and .json files.
Learn more

Commit Message and API Parameters

Update Release Repo and Revert PR now have a Commit Message setting. Merge PR supports API Parameters passed to your Git provider's merge API, such as merge_method on GitHub or squash on GitLab. Branch protection and required checks still apply. Learn more

Signed commits with a GitHub App

Update Release Repo now creates verified, signed commits when you use a GitHub App connector and turn on Enable Signed Commit for GitHub in the Git Experience default settings, so you can use signed-commit branch protection on the branches it creates.
Learn more

Services, Plugins and ApplicationSets

Vault plugin support for Kustomize

The Harness Vault plugin can now inject secrets from Harness Secret Manager into Kustomize manifests. Connect the application by setting spec.source.plugin.name to argocd-harness-plugin, and use plain Secret manifests rather than secretGenerator.
Learn more

JEXL expressions in the GitOps agent

The GitOps agent now supports JEXL expressions, extending the Harness expressions you can already use in GitOps application manifests. This helps when a plain Harness expression is not enough to compute a value in your manifests.
Learn more

Deployment Repository manifest deprecated

The Deployment Repository manifest for GitOps services is deprecated. Move to App Set Reference so Fetch Linked Apps and PR pipelines keep working, then delete the DeploymentRepo manifests and keep the Release Repository. Learn more

App Set Reference overrides

Override a service's App Set References with the Application Set override type in Global Environment and Service Specific overrides. Use Global Environment overrides to apply a change across services and Service Specific overrides for a single service. Harness Support enables this.
Learn more

Agents, Clusters and Argo CD

Custom Helm release names for agents

Set your own Helm release name when installing an agent to avoid naming conflicts. If you bring your own Argo CD, pass its actual Redis and repo-server service names so the agent health check finds them.
Learn more

GitOps agent metrics

The agent now reports metrics to Harness, shown on a new Metrics tab, or you can scrape its Prometheus-style endpoint yourself. Requires agent 0.129.1 or later and enablement through Harness Support.
Learn more

Readable AppProject names on import

New AppProjects, including imported Argo CD projects, now have names in the format <org>-<project>, making them easier to recognize. Existing AppProjects are not renamed.
Learn more

Argo CD import history

GitOps now saves a record of each Argo CD import on the agent's History Audit tab, listing the services, environments, and clusters created or linked, who ran it and when, and a status. The default view covers the last 7 days.
Learn more

Labels and annotations on clusters

Add custom labels and annotations to clusters to organize and filter them. This makes it easier to group clusters by environment, region, or team as your fleet grows.
Learn more

Argo CD 3.5

The GitOps agent and service now bundle Argo CD 3.5.6, following 3.5.1 and 3.5.3 earlier in the quarter. Upgrade your agents to pick up the latest upstream Argo CD improvements.

What's Next

We are continuing to invest in application operations, PR pipelines, and agent observability for GitOps. To explore everything GitOps offers today, head to the Harness documentation.

Get Started

Explore the documentation linked above for each feature, or reach out to your Harness account team to see these capabilities in your environment.