For the complete documentation index, see llms.txt. This page is also available as Markdown.

What's Supported

Supported CD features and integrations.

This topic lists the supported CD features and integrations you can use in Harness for deploying and verifying your apps.

For a comprehensive list that includes all Harness modules, go to Supported platforms and technologies.

Platform features for all deployment types

Access control

Role-based access control (RBAC) lets you control who can access your resources and what actions they can perform on the resources. To do this, a Harness account administrator assigns resource-related permissions to members of user groups.

Secrets management

Harness offers a built-in Secret Management feature for securely storing and using encrypted secrets. Additionally, the platform supports cloud provider secret management services, as shown in the table below.

Provider Name
Key Encryption Support
Encrypted Data Stored with Harness
Support for Referencing Existing Secrets

AWS KMS

Yes

Yes

No

AWS Secret Manager

Yes

No

Yes

Hashicorp Vault

Yes

No

Yes

Azure Key Vault

Yes

No

Yes

Google KMS

Yes

Yes

No

For more information, see Secrets Management overview.

Delegates

The Delegate is a lightweight worker process packaged and distributed by Harness using different image types. Each Delegate image is identified by a delegate name, and the image type is specified using a tag.

Image Type
Image Tag
Image Description

DELEGATE

yy.mm.xxxxx

The release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform.

DELEGATE-MINIMAL

yy.mm.xxxxx.minimal

The minimal tag is appended to the release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform.

DELEGATE FIPS

yy.mm.xxxxx-fips

The release year, month, and version in dot-separated format. FIPS (Federal Information Processing Standard) compliant images compatible only with FIPS SMP and is not supported for SaaS environments.

DELEGATE FIPS-MINIMAL

yy.mm.xxxxx.minimal-fips

The minimal-fips tag is appended to the release year, month, and version in dot-separated format. FIPS (Federal Information Processing Standard) compliant images compatible only with FIPS SMP and is not supported for SaaS environments.

DELEGATE-LEGACY

latest

Delegate that auto upgrades with no flexibility to turn off auto upgrade (DEPRECATED)

AuthN

Authentication is the process of verifying a user’s identity before granting access to an account. In Harness, administrators can configure authentication settings to control how users sign in and manage access to the organization’s account.

For additional details, refer to the Authentication Overview.

SSO Type
SSO Providers
Authentication Supported
Authorization Supported (Group Linking)
SCIM Provisioning

SAML 2.0

Okta

Yes

Yes

Yes

Microsoft Entra ID

Yes

Yes

Yes

Others

Yes

Yes

No

OneLogin

Yes

Yes

Yes

OAuth 2.0

Github

Yes

No

N/A

GitLab

Yes

No

N/A

Bitbucket

Yes

No

N/A

Google

Yes

No

N/A

Azure

Yes

No

N/A

LinkedIn

Yes

No

N/A

LDAP (Delegate connectivity needed)

Active Directory

Coming soon

Coming soon

N/A

Open LDAP

Coming soon

Coming soon

N/A

Oracle LDAP

Coming soon

Coming soon

N/A

Notifications

Git experience

Harness Git Experience allows you to store your resource configurations, such as pipelines and input sets, in Git. You can use Git as the single source of truth and modify your configurations using your Git credentials.

Supported Git providers for Harness Git Sync include:

  • GitHub

  • Bitbucket Cloud

  • Bitbucket Server

  • Azure Repos

  • GitLab

Supported Harness resources (entities) in Git using Harness Git Experience:

  • Pipelines

  • Input sets

  • Templates

  • Services

  • Environments

  • Infrastructure Definitions

Artifact Source templates are not supported with Git Experience.

Accounts, orgs, projects

The following table lists the resources that are available at various scopes in Harness:

Resources

Account

Org

Project

Pipeline

No

No

Yes

Services

Yes

Yes

Yes

Environments

Yes

Yes

Yes

Git Management

No

No

Yes

Connectors

Yes

Yes

Yes

Secrets

Yes

Yes

Yes

SMTP Configuration

Yes

No

No

Templates

Yes

Yes

Yes

Audit Trail

Yes

Yes

Yes

Delegates

Yes

Yes

Yes

Governance

Yes

Yes

Yes

Kubernetes
  • Supported connectors for deployment:

    • Kubernetes connector

      • Username and password

      • Client key and secret

      • OIDC authentication

      • Kubernetes service account

      • Assume role binding on delegate configuration

    • Google Cloud connector (GKE authentication)

      • Service Account

      • Google Cloud Role on Delegate

      • Workload Identity

    • Azure Cloud Connector (AKS Authentication)

    • AWS Cloud Connector (EKS Authentication)

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud Support

  • Supported platforms for deployment:

    • Self Hosted Kubernetes

    • Google Kubernetes Engine

    • Azure Kubernetes Engine

    • AWS Elastic Kubernetes Service

    • Red Hat OpenShift

  • Versions and tooling support:

    • Kubectl Client Versions:

      • We support what each of the Cloud Providers support. We recommend users to keep their binary versions up to date.

      • By default, Harness ships with kubectl client version 1.24.3

      • Harness has certified versions: 1.16, 1.25, 1.26, 1.27, 1.28.7, 1.29, 1.30, and 1.31

      • You must install the respective client version on the delegate for Harness to leverage it.

    • Tooling:

      • OpenShift - oc client binary

      • Kustomize - kustomize binary

      • Helm - Helm v3.15.4 (shipped); Helm v3 versions up to v3.21.1 and Helm v4 are supported

  • Limitations:

    • Helm:

      • Helm Hooks are not supported for this swimlane. Harness manages and orchestrates the manifests and their release.

      • There is a known open Helm issue (helm/helm#10748) where Helm does not remove a resource on upgrade if another resource with the same Kind but a different apiVersion exists in the same release. Helm merged a fix but subsequently reverted it due to a regression, and the issue remains unresolved.

      • Kustomize:

        • Kustomize Patches are only supported in YAML, not JSON

        • Kustomize Containerized Plugins are not supported

        • Kustomize manifests and patches do not support the custom remote manifest feature.

      • Harness managed resources:

        • Deployment

        • Secrets

        • ConfigMap

        • StatefulSet

        • HorizontalPodAutoScalar

        • PodDisruptionBudget

  • Deployment Performance

    • Helm deployments might start failing at the delegate due to a large index.yaml files. This causes a CPU spike on the delegate. If you do not provide enough resources to the delegate, you might see failures in pipeline executions.

    • Certified Limits:

      • Index.yaml file size limit 15Mb

      • 5000 Helm charts have been deployed

      • Kubernetes delegate size: 8GB, 2 CPU

      • 10 parallel deployments

  • Supported integrations:

    • Traffic Shifting for Advanced Deployment Strategies:

      • Istio

      • Nginx Ingress Controller

    • All manifest type sources for fetching Kubernetes resources:

    • For Helm Chart Type Manifests we also support:

      • Generic Git Provider

      • Google Cloud Storage

      • Amazon S3 Storage

      • Helm OCI Repository (ACR, ECR, GAR, Artifactory)

      • Helm HTTP Server Repository (Nexus, Artifactory)

    • Artifact repository supported to deploy with manifest:

      • DockerHub

      • Amazon Elastic Container Registry

      • Google Container Registry

      • Azure Container Registry

      • Custom Artifact Source

      • Google Artifact Registry

      • Github Package Registry

      • Nexus 3 (Sonatype 3.50.0 and previous supported)

      • Artifactory

For details on what you can deploy, go to What Can I Deploy in Kubernetes?.

Kubernetes version support

The following versions are tested and supported for Kubernetes Canary, Rolling, and Blue/Green deployments:

  • 1.13.0

  • 1.14.0

  • 1.15.0

  • 1.16.0

  • 1.17.0

  • 1.18.0

  • 1.19.4

  • 1.20.0

  • 1.21.0

  • 1.22.0

  • 1.23.0

  • 1.24.3

  • 1.24.9

  • 1.25.6

  • 1.26.0

  • 1.27.0

  • 1.30.10

  • 1.31.8

  • 1.33.4

  • 1.34.0

Go to Delegate-required SDKs to view other tools and versions included in Harness.

Guidelines:

  • Harness will officially support 3 previous versions from the last stable release. For example, the current most recent stable release is 1.25.6, and so Harness supports 1.24, 1.23, and 1.22.

  • Harness supports any other versions of Kubernetes you are using on a best effort basis.

  • Harness commits to support new minor versions within 3 months of the first stable release. For example, if the stable release of 1.25.6 occurs on April 15th, we will support it for compatibility by July 15th.

Kubernetes Java client compatibility

Harness uses the Kubernetes Java client (io.kubernetes:client-java) version 22.0.1, which is generated from the Kubernetes 1.31 OpenAPI specification. This client is compatible with Kubernetes API servers across multiple versions due to Kubernetes API backward and forward compatibility guarantees.

Compatibility matrix:

Kubernetes API Server Version
Harness Client Support Status
Notes

1.13 - 1.31

Fully Supported

All features tested and certified

1.32 - 1.34

Partially Supported

Deployments work; manifests using fields added after 1.31 cause validation errors (see limitations below)

1.35 and later

Partially Supported

Deployments work; manifests using fields added after 1.31 cause validation errors (see limitations below)

Important notes:

When deploying to Kubernetes clusters running versions 1.32 and above, be aware of the following limitations:

  • New API fields: Kubernetes versions after 1.31 introduce new optional fields in core resource types (Pod, Deployment, DaemonSet, StatefulSet, Job, CronJob).

  • Validation behavior: If your manifests contain fields that were added in Kubernetes versions 1.32 and later, Harness will throw a KubernetesYamlException during manifest validation.

  • Affected fields: The following fields added between Kubernetes 1.31 and 1.35 are not recognized by the current client:

    • spec.hostnameOverride, spec.resources, spec.workloadRef (in PodSpec)

    • containers[].restartPolicyRules (in Container and EphemeralContainer)

    • containers[].lifecycle.stopSignal (in Lifecycle)

    • spec.securityContext.seLinuxChangePolicy (in PodSecurityContext)

    • spec.volumes[].projected.sources[].podCertificate (in VolumeProjection)

    • containers[].env[].valueFrom.fileKeyRef (in EnvVarSource)

Workaround:

If you encounter validation errors when using these newer fields, you have two options:

  1. Remove the new fields: Remove any Kubernetes 1.32+ fields from your manifests. These fields are optional additions and your deployments will work without them on supported Kubernetes versions.

  2. Use kubectl apply: Use the Harness Apply step instead of the standard deployment steps. The Apply step uses kubectl directly and bypasses the Java client validation, allowing newer fields to pass through to your cluster.

Helm notes

Helm chart dependencies are not supported in Git source repositories. Helm chart dependencies are supported in Helm Chart Repositories.

Azure AKS clusters

To use an AKS cluster for deployment, the AKS cluster parameter disableLocalAccounts can be set either true or false.

Native Helm
  • Overview:

  • Supported connectors for deployment:

    • Kubernetes Connector

      • Username + Password

      • Client Key and Secret

      • OIDC Authentication

      • Kubernetes Service Account

      • Assume Rolebinding on Delegate Configuration

    • Google Cloud Connector (GKE Authentication)

      • Service Account

      • Google Cloud Role on Delegate

      • Workload Identity

    • Azure Cloud Connector (AKS Authentication)

    • AWS Cloud Connector (EKS Authentication)

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud Support

  • Supported platforms for deployment:

    • Self Hosted Kubernetes

    • Google Kubernetes Engine

    • Azure Kubernetes Engine

    • AWS Elastic Kubernetes Service

    • Red Hat OpenShift

  • Versions and tooling support:

    • Helm Client Versions: Harness ships Helm v3.15.4; Helm v3 versions up to v3.21.1 and Helm v4 are supported

    • We support what each of the Cloud Providers support, we recommend users to keep their binary versions up to date

    • Tooling:

      • OpenShift - oc client binary

      • Kustomize - kustomize binary

      • Helm - Helm v3.15.4 (shipped); Helm v4 is also supported

  • Limitations:

    • Helm v2 is deprecated and not recommended for new deployments. Helm v3 and v4 are supported.

    • Helm 3 is the default for Harness Helm Chart Deployments.

    • Helm Plugins are not supported

    • Only Basic Deployment Strategy supported (No Canary or Blue-Green Support Out of the box)

  • Supported integrations:

    • Manifest Sources for fetching Helm Chart:

      • Github

      • Gitlab

      • Bitbucket

      • Generic Git Provider

      • Custom Remote Source Repository

      • Google Cloud Storage

      • Amazon S3 Storage

      • Helm OCI Repository (ACR, ECR, GAR, Artifactory)

      • Helm HTTP Server Repository (Nexus, Artifactory)

      • Harness Local File Store

    • Artifact Repository for Container Images to deploy with Chart:

      • DockerHub

      • Amazon Elastic Container Registry

      • Google Container Registry

      • Azure Container Registry

      • Custom Artifact Source

      • Google Artifact Registry

      • Github Package Registry

      • Nexus 3 (Sonatype 3.50.0 and previous supported)

      • Artifactory

Notes

Helm chart dependencies are not supported in Git source repositories. Helm chart dependencies are supported in Helm Chart Repositories.

Amazon ECS
  • Overview:

  • Supported connectors for deployment:

  • AWS Cloud Connector

    • IRSA

    • Access Key and Secret Key

    • IAM Role

    • GovCloud Support

  • Supported platforms for deployment:

    • AWS Cloud, any region

    • AWS - Launch Types:

      • Amazon ECS - EC2 - Generally Provisioned Instances

      • Amazon ECS - EC2 - Spot Backed Instances

      • Amazon ECS - Fargate

  • Versions and tooling support:

    • AWS SDK

  • Supported integrations:

    • ECS Service Discovery - Supported via Service Definition

    • ECS Circuit Breaker - Supported via Service Definition

    • Artifact Repository:

      • DockerHub

      • Amazon Elastic Container Registry

      • Azure Container Registry

      • Custom Artifact Source

      • Github Package Registry

      • Nexus 3 (Sonatype 3.50.0 and previous supported)

      • Artifactory

  • Limitations:

Amazon AMI/ASG
  • Overview:

  • Supported connectors for deployment:

    • AWS cloud connector

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud Support

  • Supported platforms for deployment:

    • AWS cloud, any region

  • Versions and tooling support:

    • AWS SDK

  • Limitations:

    • Harness Code Repository is not supported for storing your configuration files, User Data, Scaling Policy script and Config File.

AWS Lambda
  • Overview:

  • Supported connectors for deployment:

    • AWS Cloud Connector

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud supported

  • Supported platforms for deployment:

    • AWS cloud, any region

  • Versions and tooling support:

    • AWS SDK

  • Supported integrations:

    • Artifact Repository Supported to Deploy with Function Definition:

      • Amazon Elastic Container Registry

      • Amazon S3

  • Limitations:

    • Harness Code Repository is not supported for storing AWS Lambda Config File, Lambda Function Definition and Lambda Function Alias Definition.

AWS SAM
  • Overview:

  • Supported connectors for deployment:

    • AWS cloud connector

      • Access key and secret key

  • Supported platforms for deployment:

    • AWS cloud, any region

  • Versions and tooling support:

    • AWS SDK

    • Harness supports standard SAM templates.

  • Supported integrations:

    • All Git providers are supported for SAM templates.

    • Currently, you cannot add artifacts to your Harness SAM service.

    • Harness Code Repository is supported for storing your Values YAML file for manifest type Values YAML.

  • Limitations:

    • Harness Code Repository is not supported for storing AWS SAM manifest when you select manifest type as AWS SAM Directory.

Traditional: WinRM
  • Overview:

  • Supported connectors for deployment:

    • AWS Cloud Connector

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud Support

    • Azure Cloud Connector (AKS Authentication)

      • Subscription Id

      • Principal and Service Account

      • GovCloud Support

  • Supported platforms for deployment:

    • AWS Cloud

    • Azure Cloud

    • Physical Datacenter

Traditional: SSH
  • Overview:

  • Supported connectors for deployment:

    • AWS Cloud Connector

      • IRSA

      • Access Key and Secret Key

      • IAM Role

      • GovCloud Support

    • Azure Cloud Connector (AKS Authentication)

      • Subscription Id

      • Principal and Service Account

      • GovCloud Support

  • Supported platforms for deployment:

    • AWS Cloud

    • Azure Cloud

    • Physical Datacenter

  • Linux SSH Setups

    • Ubuntu Version 22+

    • RHEL9 (Red Hat Enterprise Linux 9)

    • SSH libraries supported:

      • SSHJ: used in our HashiCorp Vault SSH integrations.

      • JSCH: used in our SSH deployment types.

      • To see the hostkey formats for these libraries, go to the SSH implementation comparison.

  • Limitations:

    • Google Compute Engine (Virtual Machine Targets)

      • Limited Support, Harness can connect to Google VMs via an SSH Key, not via Google Cloud Authentication

Tanzu Application Service (formerly Pivotal Cloud Foundry)
  • Supported connectors for deployment:

    • Tanzu Connector

      • Endpoint URL, Username and Password

  • Supported platforms for deployment:

    • On Premise Cloud Foundry Installations

    • VMware Tanzu Platform

  • Versions and tooling support:

    • Binary Versions:

      • CF CLI v7

  • Limitations:

Google Functions
  • Supported connectors for deployment:

    • Google Cloud Connector

    • Service Account

  • Supported platforms for deployment:

    • Google Cloud, any region

  • Versions and tooling support:

    • Google SDK. Supported versions:

      • Google Functions Gen 1

      • Google Functions Gen 2

  • Deployment strategies:

    • Google Functions Gen 1: Basic.

    • Google Functions Gen 2: Basic, blue green, canary.

  • Supported integrations:

    • Artifact Repository:

      • Google Cloud Storage

      • Google Cloud Storage and Google Cloud Source (Gen 1 Only)

Google Cloud Run
  • Supported connectors for deployment:

    • Google Cloud Connector

      • Service Account

      • Google Cloud Role on Delegate

      • Workload Identity

      • OIDC authentication support

  • Supported platforms for deployment:

    • Google Cloud, any region

  • Versions and tooling support:

    • Google SDK

    • gcloud CLI

  • Deployment strategies:

    • Cloud Run Services: Basic and Canary

    • Cloud Run Jobs: Task-based execution

  • Supported integrations:

  • Supported workload types:

    • Google Cloud Run Services (stateless containerized applications with auto-scaling)

    • Google Cloud Run Jobs (task-based execution, batch processing, scheduled tasks)

  • Limitations:

    • Requires containerized execution environment for Cloud Run Jobs

Google Managed Instance Groups (MIG)
Spot Instances
  • Supported connectors for deployment:

    • Spot Connector

      • AccountID + API Token

  • Supported platforms for deployment:

    • AWS cloud, any region

  • Limitations:

    • Deployment Behavior:

      • Incremental Traffic Shifting for SpotInst Deployment is not supported

      • VM-based Deployments are supported via Elastigroup configuration

Serverless.com Framework
  • Overview:

  • Supported connectors for deployment:

    • AWS Cloud Connector

      • IRSA

      • Access Key and Secret Key

      • IAM Role

  • Supported platforms for deployment:

    • AWS cloud, any region

  • Versions and tooling support:

    • Supported Binary Versions:

      • serverless.com 2.x

      • serverless.com 3.x

      • serverless.com 4.x

      • serverless.com 1.x (deprecated - limited support, not all capabilities supported)

  • Limitations:

    • Deployment Behavior:

      • Harness only supports AWS Lambda Functions to be deployed via Serverless.com Framework

      • Harness builds and deploys Lambda Functions. You cannot split up the tasks to build functions and deploy functions separately as part of Harness support.

    • Not supported application types:

      • Google Functions

      • Azure Functions

    • Basic deployment supported. No out-of-the-box canary and blue green deployment supported.

  • Supported integrations:

    • Serverless.com plugins:

      • Harness supports all the Serverless.com plugins. Please make sure they are compatible with the version of Serverless.com you are using.

    • Artifact Repository:

      • DockerHub

      • Amazon Elastic Container Registry

      • Artifactory

      • Amazon S3

    • Harness Code Repository is supported for storing your Values YAML file for manifest type Values YAML.

  • Limitations:

    • Harness Code Repository is not supported for storing Serverless Lambda Manifest when you select manifest type as Serverless Lambda Manifest as well as for storing Config File.

Azure WebApps
  • Supported connectors for deployment:

    • Azure Cloud Connector (AKS Authentication)

  • Supported platforms for deployment:

    • Azure cloud, any Region

  • Versions and tooling support:

    • Azure SDK

  • Limitations:

Azure Functions
Builds in CD

Continuous Integration (CI) can be performed in Harness using the module and CI pipelines.

If you are using Harness Continuous Delivery (CD) but not Harness Continuous Integration (CI), you can still perform CI using the Jenkins step in your CD stage.

Harness integrates with Jenkins, enabling you to run Jenkins jobs and dynamically capture inputs and outputs from the jobs.

Harness has been tested with the following versions of Jenkins:

GitOps

Harness GitOps lets you perform GitOps deployments in Harness. You define the desired state of the service you want to deploy in your Git manifest, and then use Harness GitOps to sync state with your live Kubernetes cluster.

GitOps supports the following:

  • GitOps reconciler:

  • Argo CD versions supported:

    • 2.8.2

    • 3.1.8 (Bundled with Helm 3.18.4 and Kustomize 5.7.0)

  • Source Repositories:

    • All Git providers.

    • HTTP Helm repos.

  • Target clusters:

    • Kubernetes clusters hosted on any platform:

      • GKE.

      • AKS.

      • EKS.

      • Other Kubernetes-compliant clusters.

      • OpenShift version 3.11, 4.x.

      • Minikube.

      • Kubernetes Operations (kops).

  • Repository Certificates:

    • TLS Certificate (PEM format).

    • SSH Known Host Entry.

  • GnuPG Keys:

    • GnuPG Public Key Data (ASCII-armored).

  • Limitations:

    • Self-hosted environments

      • Agents installed in custom namespaces are not yet supported.

Local (Harness Community Edition)

Harness CD Community Edition is a lightweight version of Harness that you can download and run on your laptop or any VM.

Harness CD Community Edition is intended to get devs started with Harness quickly without having to sign up for a Harness SaaS account.

Custom

For non-native deployments, Harness provides a custom deployment option using Deployment Templates.

Harness supports the following infrastructure provisioning tools:

Terraform version support

Harness does not include Terraform on the Harness Delegate. You must install Terraform on the Delegate when using Terraform in Harness. For more information, go to Terraform How-tos.

Harness supports the following Terraform versions:

  • v1.3.5

  • v1.1.9

  • v1.0.0

  • v0.15.5

  • v0.15.0

  • v0.14.0

Here's an example install script for the Harness Delegate:

Some Harness features might require specific Terraform versions.

NOTE

Harness also supports Terraform Cloud and Enterprise.

Manifests, specifications, config files, and other deployment files can be pulled from the following providers:

The following table lists where you can store your manifests or config files for each integration.

Github

Gitlab

Bitbucket

Harness File Store

Any Git

OCI Helm

HTTP Helm

AWS S3

Custom

Google Cloud Storage

Inherit from manifest

Kubernetes

Values YAML

Kustomize

Kustomize Patches

OpenShift Template

OpenShift Params

AWS ECS

AWS SAM

Helm Chart

Serverless.com Framework

SSH

WinRM

Azure Web Apps

Google Cloud Function

The following table lists supported manifest overrides for each integration.

Deployment Type

Supported Manifest Overrides

Kubernetes

  • Values YAML

  • OpenShift Param

  • Kustomize Patches

Helm

  • Values YAML

  • Helm Repo Override

AWS ECS

  • ECS Task Definition

  • ECS Service Definition

  • ECS Scalable Target

  • ECS Policy Scaling

AWS ASG

N/A

AWS Lambda

  • AWS Lambda Function Definition

  • AWS Lambda Function Alias Definition

AWS SAM

  • Values YAML

  • AWS SAM Directory

Azure Web Apps

  • Application Settings

  • Connection Strings

Azure Functions

N/A

Tanzu Application Services

  • TAS Manifests

  • TAS Vars

  • TAS Autoscaler

SSH

N/A

WinRM

N/A

Serverless.com Framework

  • Values YAML

  • Serverless AWS Lambda Manifest

Google Cloud Functions

N/A

Google Cloud Run

N/A

Spot Elastigroup

N/A

All artifact sources are covered in CD artifact sources.

  • Harness Artifact Registry

  • Docker registry on any platform

  • Google Container Registry (GCR)

  • Google Cloud Storage (GCS)

  • Google Artifact Registry

  • Amazon Elastic Container Registry (ECR)

  • AWS S3

  • Azure Container Registry (ACR)

  • Azure DevOps Artifacts

  • Nexus 2 and Nexus 3 (Sonatype 3.50.0 and previous supported)

  • Artifactory

  • Jenkins

  • Bamboo

  • Github packages

  • HTTP Helm

  • OCI Helm

  • Custom artifact source

Harness uses Metadata only when downloading artifact sources.

For pulling Docker images from Docker repos, Harness is restricted by the limits of the Docker repo. For example, Docker Hub limits.

The maximum number of artifact image tags fetched by Harness that is 10000.

The following table lists Harness integrations and their artifact source support:

Harness Artifact Registry

Docker Hub

ECR

GCS

ACR

Artifactory

Nexus 3

Custom

Google Artifact Registry

Github Artifact Registry

Jenkins

AWS S3

Kubernetes

Helm

AWS ECS

AWS ASG

AWS Lambda

Azure Web Apps

Azure Functions

Tanzu

SSH

WinRM

Serverless.com Framework

Google Cloud Function

Google Cloud Run

Google MIG

You can use the following ticketing systems for creating and updating tickets, and as approval gates:

Approval workflows

Harness provides flexible approval workflows that can be integrated into your deployment pipelines:

  • Harness Approvals: Native approval steps that can be configured with user groups, automatic approvals, and custom approval logic

  • Jira Approvals: Integrate with Jira to use existing ticket workflows for deployment approvals

  • ServiceNow Approvals: Leverage ServiceNow change management processes for deployment gates

  • Custom Approvals: Build custom approval logic using conditional execution and API integrations

Key capabilities:

  • User group-based approvals with combined or any-member logic

  • Auto-reject previous deployments when new ones reach approval stage

  • Include stage execution details for informed decision-making

  • Timeout and failure strategy configuration

  • Approval notifications via email, Slack, MS Teams

For detailed documentation, go to Approvals.

For frequently asked questions about ticketing and approvals in CD, go to Approvals and Ticketing FAQs.

Note: All detailed approval and ticketing FAQs have been moved to the dedicated Approvals and Ticketing FAQs page for better organization and easier reference.

Harness Policy As Code uses Open Policy Agent (OPA) as the central service to store and enforce policies for the different entities and processes across the Harness platform.

You can centrally define and store policies and then select where (which entities) and when (which events) they will be applied.

Currently, you can define and store policies directly in the OPA service in Harness.

Soon, you will be able to use remote Git or other repos (e.g. OCI-compatible registries) to define and store the policies used in Harness.

Policy as Code limitations

  • When configuring a policy for testing, users must have a pipeline that has a policy run against it (success or failed) to capture the pipeline's expanded JSON for the policy studio testing terminal.

  • Policies can only be run against one document (one JSON payload sent for OPA evaluation). You cannot run a policy against multiple documents.

  • Not all Harness entities are supported with policies:

    • For CD: service, environment, infrastructure, and overrides are on the roadmap for integration.

    • For Platform: service account, API key, and token are on the roadmap for policy integration.

    • For other product modules: entities will be added as needed.

  • Harness does not support OPA bundles.

  • Harness does not support data imports from external sources.

  • Harness does not support allow, to support this use case you need to invert the logic, Harness OPA supports deny and not allow.

For frequently asked questions about OPA policies and governance, go to OPA FAQs.

Note: All detailed governance and OPA policy FAQs have been moved to the dedicated OPA FAQs page for better organization and easier reference.

Notes

  • AWS and Azure GovCloud: Harness is now certified in Azure GovCloud and AWS GovCloud.

Harness Self-Managed Enterprise Edition (SMP) including offline Environments

All CD features supported in Harness SaaS are also supported in Self-Managed Enterprise Edition with the following exceptions:

  • Dashboards: Harness CD Dashboards might not be completely functional with a bundled Timescale community edition version installation.

  • Triggers: The feature flag CD_GIT_WEBHOOK_POLLING must be enabled for Github polling with two factor authentication. For more information, go to Polling frequency.

  • ServiceNow: ServiceNow versions Utah and earlier are supported.

  • Jira: Jira on-premise versions < 9.0 are supported. To support Jira on-premise >= 9.0, the feature flag SPG_USE_NEW_METADATA must be enabled.

  • Policy as Code: Harness Git Experience support for OPA policies is not supported in Self-Managed Enterprise Edition.

  • Harness AI: To support Harness AI in Self-Managed Enterprise Edition running in an offline environment, you must add https://harness.openai.azure.com to your allowlist.

Deploy pipeline log streaming

Harness CD supports streaming deploy pipeline stage execution logs from your self-managed delegate to your own observability backend, such as Grafana Loki, Splunk, Datadog, or Elasticsearch. When enabled, the delegate writes CD execution logs as structured JSON to stdout in parallel with the standard Harness Log Service. A log collector such as OpenTelemetry Collector, Fluent Bit, or Vector then forwards those logs to your backend.

Go to Stream pipeline logs to set this up.


Active CD Feature flags

Some Harness CD features are released behind feature flags to get feedback from specific customers before releasing the features to the general audience. Feature development statuses are categorized as Beta, GA, or Limited GA.

The following table describes active feature flags relevant to Harness CD.

To enable a feature flag in your Harness account, contact Harness Support.

Flag
Description

CDS_GITOPS_POST_PROD_ROLLBACK

Enables post-production rollback for GitOps applications from the Services dashboard. After a successful pipeline deployment, a Rollback button appears in the Services tab allowing you to execute the pipeline's rollback steps. Go to Post-production rollback from the Services dashboard for more information. This feature is in Beta.

OPA_GITX_PARITY

Enables enhanced Git Experience UI features for OPA policies. This feature is in Limited GA.

OPA_GITX_DIRECT_FETCH

Enables direct batch fetch of policy content from Git during evaluation, improving performance and error reporting. This feature is in Limited GA.

CDS_AWS_DESCRIBE_REGIONS_OPTIONAL

When enabled, Harness uses sts:GetCallerIdentity instead of ec2:DescribeRegions for AWS connector validation, removing the EC2 IAM permission requirement. Requires delegate version 889xx or later. For details, go to DescribeRegions and connector validation. This feature is in Limited GA.

CDS_HELM_IMPROVED_SOPS_SUPPORT_FOR_SERVICE_HOOKS

For Native Helm, enables per-task values override directories and service hook variables (VALUES_OVERRIDE_DIRECTORY, OVERRIDE_FILES) for SOPS and custom overrides. Requires delegate 26.03.88700 or later. See SOPS and values overrides in Native Helm service hooks. This feature is in Limited GA.

CDS_GITX_WEBHOOK_SYNC_ENTITY_METADATA

Enables automatic metadata sync (name, description, and tags) for service, environment, and infrastructure entities during bidirectional sync. When enabled, metadata changes committed to the default branch in Git are automatically propagated to the corresponding entity in Harness. This sync applies only to the default branch; metadata changes on other branches are not synced. This feature is in Limited GA.

OPA_INCLUDE_GROUP_ROLE_ASSIGNMENTS

When enabled, OPA policy evaluation includes roles inherited through user groups in input.metadata.roleAssignmentMetadata for USER principals, not only roles assigned directly to the user. Use this when OPA policies check roleAssignmentMetadata to allow or deny actions based on RBAC roles. When disabled (default), only direct user role assignments are included, so policies may not see group-inherited roles. This is a behavior change for existing OPA policies. Review policies before enabling. This feature is in Limited GA.

PIPE_OPA_DISABLE_EVALUATION_DATA_IN_LISTING

When enabled, the policy evaluations list API (GET /api/v1/evaluations) no longer returns evaluation payload data inline. The details field will be null in list responses; full evaluation details remain available via the individual evaluation endpoint (GET /api/v1/evaluations/{id}). In the UI, the Policy Sets column in Governance > Policy Evaluations shows a View Details button instead of inline policy set names. This change is part of memory optimisation efforts to improve service reliability for accounts with large evaluation payloads. This feature is in Limited GA.

PIPE_OPA_STRIP_LARGE_OUTPUT_FROM_POSTGRES

When enabled, Harness replaces any OPA policy output larger than half the evaluation input size with a small placeholder recording the removed output's size before storing the evaluation. This is a safety check to prevent oversized policy outputs from bloating evaluation storage. Policy status, deny messages, severity, and error details are not affected. This feature is in Beta.

PIPE_FAIL_USER_MARKED_FAIL_ALL_INTERRUPT_WITHOUT_LEAF_NODES

When enabled, this flag ensures that interrupting a pipeline execution (for example, marking it as failed or expiring it) correctly stops all running tasks and releases resources, preventing resource locking and potential pipeline stalls. This is a Beta fix

CDS_CONTAINER_STEP_DELEGATE_SELECTOR_PRECEDENCE

Enable this feature to honor delegate selector precedence in container steps, including git clone operations. When enabled, delegate selectors defined at the pipeline, step group, or step level will take precedence over connector-level delegate selectors for container-based deployments. This is a Beta feature.

CDS_ENABLE_TERRAGRUNT_V1_SUPPORT

Enables support for Terragrunt versions 0.78.0 and later, which introduced breaking changes in command formats. When enabled, Harness automatically detects the Terragrunt version and uses the appropriate command format (new --all flag instead of run-all subcommand, --non-interactive instead of --terragrunt-non-interactive, and updated workspace command structure). The system falls back to legacy commands for versions below 0.78.0. For more information, refer to the Terragrunt documentation. This feature is in Limited GA.

PIPE_STORE_TEMPLATE_REFERENCE_SUMMARY_PER_EXECUTION

Enables users to view the template version used during pipeline execution, helping them identify the exact version label applied at runtime. This feature is in Limited GA.

PIPE_BARRIERS_FOR_CHAINED_PIPELINES

Enables users to configure barrier synchronization across parent and child pipelines, allowing child pipelines to reference and use barriers defined in parent pipelines via runtime inputs for coordinated deployments. This feature is in Limited GA.

PIPE_CREATE_EDIT_PERMISSION_SPLIT_MIGRATION, PIPE_CREATE_EDIT_PERMISSION_SPLIT

Enables users to configure separate Create and Edit authorization grants for pipelines and templates, offering more granular RBAC control. Enabling this feature requires a migration of existing resources, which will be guided by Harness Support. This feature is in Limited GA.

PIPE_PROJECT_LEVEL_EXECUTION_CONCURRENCY, PIPE_ENABLE_QUEUE_BASED_PLAN_CREATION

Enables users to configure Project-Level Pipeline Execution Concurrency, allowing them to allocate execution capacity across High-Priority and Low-Priority partitions. This feature is in Limited GA.

PIPE_POPULATE_REQUIRED_AND_DESC_METADATA_INTO_REFERENCING_ENTITY

Enables users to preserve the Required flag and Description metadata for Service and Environment variables in Pipelines and Templates, ensuring these attributes are retained when used as runtime inputs. This feature is in Limited GA

PIPE_GITX_DISABLE_SKIP_GIT_WEBHOOK_REGISTRATION

Enables users to register GitX webhooks without creating them in Git providers, allowing webhook setup via an intermediary service without requiring connector-level registration permissions. This feature is in Limited GA.

CDS_DEPLOY_SERVICE_IN_PARALLEL_FIX

Enables users to retain the selected chart version when toggling the Deploy Service in Parallel option, even when both are configured as runtime inputs. This feature is in Limited GA.

PIPE_DISABLE_PIPELINE_NOTIFICATIONS_ON_ROLLBACK

Enables users to suppress independent PIPELINE_START and PIPELINE_SUCCESS notifications during rollback, ensuring that only the main pipeline's PIPELINE_FAILED notification is sent. This feature is in Limited GA.

CDS_K8S_NOT_ADD_TRAFFIC_ROUTING_TO_CANARY_WORKLOAD

Enables users to prevent Virtual Services from being deleted during the Canary Delete step in Kubernetes deployments, preserving traffic routing configurations during rollback. This feature is in Limited GA.

CDS_ASG_MULTI_DEPLOY_ROLLBACK_SUPPORT

Enables users to deploy multiple ASGs in a single stage for the same service, environment, and infrastructure, with automatic parallel rollback triggered on failure. This feature is in Limited GA.

PIPE_FAIL_ALL_FAILURE_STRATEGY

Enables users to configure fail fast behavior in parallel executions, where a failure in any step or stage immediately fails the pipeline and triggers the configured failure strategy. This feature is in Limited GA.

PIPE_ENABLE_INPUT_SET_FILTER

Enables users to view applied Input Sets in the Inputs tab as clickable links and see them in the trigger summary on the execution history page. This feature is in Limited GA.

PIPE_ENABLE_GITHUB_ENTERPRISE_PROVIDER_FLOW

Enables users to integrate their GitHub Enterprise instance using Harness’s OAuth provider configuration, instead of legacy token-based connectors. Harness's built-in Secret Manager is not supported with this provider flow, you must use a custom Secret Manager accessible to your delegate. This feature is in Limited GA.

PIPE_SUPPORT_MULTIPLE_TIMEZONES_IN_CRON_TRIGGERS

Enables users to select timezones for Cron triggers using IANA Time Zone names, providing more control over when pipelines are triggered. This feature is in Limited GA.

PIPE_EXECUTION_ID_FILTER

Enables users to filter pipeline executions by build ID, making it easier to quickly locate specific runs without scrolling through large execution lists. This feature is in Limited GA.

PIPE_ENABLE_QUEUED_BASED_CUSTOM_TRIGGERS

Harness now supports custom webhook trigger execution via the Queue Service, improving reliability and scalability. This ensures webhook triggers are processed efficiently even under high load, without one customer's activity impacting others. This feature is in Limited GA.

CDS_ENABLE_STEADY_STATE_CHECK_WITHOUT_MANAGED_WORKLOADS

Enables users to run Service PreHooks for Kubernetes CronJob workloads during the Wait for Steady State phase. Previously, PreHooks did not trigger for CronJobs. This feature ensures PreHooks are executed consistently across workload types. This feature is in Limited GA.

CDS_OVERRIDES_DISABLE_ENV_API_UPDATES

Enables users to view environment variable references and YAML overrides more accurately in the UI. Previously, secrets continued to appear as referenced in an environment even after removal. This fix improves clarity in the environment configuration view. This feature is in Limited GA.

CDS_AWS_LAMBDA_ECS_TAG_SUPPORT

Users can now create, update, and delete tags in AWS Lambda and AWS ECS deployments, ensuring that all specified tags in the YAML manifest are correctly propagated during the deployment process and accurately reflected in the AWS Console. This feature is in Limited GA.

CDS_SERVICE_DASHBOARD_SIMPLIFICATION

Improves Service Dashboard load time by optimizing API calls and relocating certain data to enhance performance. The service dashboard graph has been moved to the Analytics tab. Users can switch between the Service and Analytics tabs at the top right of the Service Dashboard page. This feature is in Limited GA.

PIPE_CUSTOM_NOTIFICATION_TEMPLATES

Enables customized notifications for all types of Pipeline Notifications and for Webhook-based Centralized Notifications. This feature is in Limited GA.

CDS_SUPPORT_HTTP_HEADER_HTTP_STEP

Allows capturing HTTP response headers, including cookies, as output variables in the HTTP step for use in downstream steps. This feature is in Limited GA.

CDS_SCM_FIX_FOLDER_PATH

Fixes file copy issues in SCM integrations where a leading / in the source path caused only a single file to be copied instead of the entire directory. This feature is in Limited GA.

CDS_AWS_CONNECTOR_REF_CDK

Expands the OIDC payload for GCS Cache steps to include additional claims, enabling fine-grained access control using custom claim attributes. This feature is in Limited GA.

CDS_AWS_LAMBDA_ROLLBACK_V2

Allows deployment of AWS Lambda artifacts larger than 50 MB from S3 and supports version rollback using aliases. This feature is in Limited GA.

CI_ENABLE_MULTILINE_OUTPUTS_SECRETS

Enables support for capturing multiline output variables from Container steps in CD pipelines, ensuring proper population and visibility in the Output tab. This feature is in Limited GA.

PIPE_USE_ORIGINAL_YAML_FOR_EXECUTION

Enables re-running pipelines with the original pipeline definition and inputs to ensure accurate reproduction and debugging of historical executions. This feature is in Limited GA.

PIPE_ADD_ORIGINAL_FAILED_CHILDREN_TO_OUTPUT

Fixes rollback handling for user-initiated failures and approval rejections by ensuring rollback strategies execute as expected. This feature is in Limited GA.

CDS_REMOVE_COMMENTS_FROM_VALUES_YAML_WITH_ESCAPE_CHARACTERS

Enables proper handling of special characters in values.yaml by removing control characters such as single (' ), double ("), and backslash (\), preventing pipeline failures.

CDS_ENFORCE_GIT_EXPERIENCE

Enables users to enforce the Git experience for environments, infrastructure, and overrides V2, ensuring consistency across all components, similar to pipelines, inputs, and templates. This feature is in Limited GA

CDS_TAS_ARTIFACT_BUNDLE_PRESERVE_PERMISSION_ON_EXTRACTION

Ensures that file permissions inside the tar.gz archive are retained when deploying Artifact Bundles for NodeJS apps to PCF (Pivotal Cloud Foundry), preventing permission issues during application startup. This feature is in Limited GA

CDS_AZURE_CLI_WEBAPP_DEPLOYMENT

Enables enhanced support for non-standard configurations and Azure CLI-based workflows for Azure Web App deployments. Available with Delegate version 85302 or later. This feature is in Limited GA

CDS_ECS_MONITOR_TASK_STATUS

Enables Harness to accurately detect failures in ECS Rolling Deployments. This feature is in Limited GA

PIPE_USE_HARNESS_CODE_FOR_INLINE_ENTITIES

Saves inline entities in the Harness Code Repository by default. This feature is in Limited GA

PIPE_DYNAMIC_PIPELINES_EXECUTION

Allows users to dynamically execute pipelines by providing pipeline YAML configurations at runtime, without requiring pre-saved configurations in Harness. This feature is in Limited GA

PIE_USE_OPTIMISED_TEMPLATE_RESOLUTION

Introduces the storeType field in YAML templates to distinguish whether a template is stored Inline or Remote. This feature is in Limited GA

OPA_IMPORT_FROM_GIT

Enables users to import OPA policies directly from Git. This feature is in Limited GA

CDS_GITOPS_OPERATOR

Enables integration of the Harness GitOps Agent with the OpenShift Certified Vendor Catalog, allowing seamless use with OpenShift OperatorHub and Red Hat Marketplace. This feature is in Limited GA

CDS_K8S_CUSTOM_YAML_PARSER

Enables support for Kubernetes sidecar containers as introduced in Kubernetes 1.28. This custom YAML parser addresses compatibility issues with the current Kubernetes Java SDK version 18.0.0, which lacks native support for sidecar configurations. This feature is in Limited GA

CDS_SKIP_INSTANCES_V2

Enables users to retry failed deployments on a subset of hosts when using traditional infrastructure. This feature is in Limited GA

CDS_ECS_BG_VALIDATION_WITH_SAME_TARGET_GROUPS

Enables users with dynamically generated load balancer configurations to successfully validate ECS Blue-Green deployment pipelines, resolving the previous validation failure. This feature is in Limited GA

CDS_CROSS_SCOPED_ENV_GROUPS

Enables users to add environments created at Account and Orgainsation level to Environment Groups. For more information, go to Harness Cross Scope Environment Groups. This feature is in Limited GA

CDS_K8S_DETAILED_LOGS

Enables users to view detailed logs of Wait For Steady State step in Kubernetes deployments. For more information, go to Harness Detailed diagnostics for K8s Deployment. This feature is in Limited GA

CDS_SERVICE_OVERRIDES_2_0_YAML_V2_SUPPORT

Ensures that overrides from environment configuration YAML are ignored when Override V2 is enabled. This feature is in Limited GA.

CDS_AWS_EKS_CLUSTER_MANUAL_CONFIGURATION

Enables users to manually configure the connection to Amazon EKS clusters by providing the endpoint and optional CA cert. This feature is in Limited GA.

CDS_ENABLE_RAW_MODE

This feature requires enabling an Account-level setting after the Feature Flag is enabled. When this setting is disabled, blank fields are treated as Null. Enabling this option will treat blank fields as empty strings. Please be aware that this change may be disruptive to existing Input Sets.

To learn more, refer Handling empty strings. This feature is in Limited GA.

CDS_AUTH_CHECK_IN_WEBHOOK_DETAILS_ENDPOINTS

Enables users to track deployment status programmatically via REST using the apiUrl from a custom trigger's JSON response. This feature is in Limited GA.

CDS_PIPELINE_ABORT_RBAC_PERMISSION_MIGRATION

Enables users to run RBAC validation before executing inline pipelines to ensure access to required environments and resources. This feature is in Limited GA.

CDS_PIPELINE_ABORT_RBAC_PERMISSION

Enables users to control Abort permission separately from other pipeline execute functions. This Feature is in Beta.

CDS_EVENT_BRIDGE_WEBHOOK and CD_TRIGGERS_REFACTOR

Enables users to trigger pipelines in real time using the newly introduced EventBridge webhooks, which can be configured with Git, Slack, or generic options (such as Nexus artifacts). This feature is in Limited GA.

PIPE_ENABLE_FILE_UPLOAD_AS_RUNTIME_INPUT

Enables users to upload files as a runtime input during execution of a pipeline using File Upload step. This feature is in Limited GA.

CDS_ENCODE_API_REQUESTS

Enables users to fetch an artifact version from Nexus during deployment. This feature is in Limited GA.

CDS_EMAIL_USE_DEFAULT_FORMATTING

Enables user to send HTML content in the email body in the Email Step. This feature is in Limited GA.

CDS_K8S_SANITIZE_COMPLETE_DRY_RUN_STEP_OUTPUT

Enables users to access Kubernetes service and job names in the exported manifest. This feature is in Limited GA.

CDS_K8S_ASYNC_STEP_STRATEGY

Enables users to view log details in the UI when a pipeline with K8s async steps times out. This feature is in Limited GA.

CDS_ASG_ROLLOUT_ROLLBACK_INSTANCE_REFRESH

Enable this feature to eliminate downtime during the Auto Scaling Group (ASG) rollback instance refresh. This feature is in Limited GA.

CDS_SPECIFY_INFRASTRUCTURES

Enables users to select all the infrastructures in the environment by choosing the All Infrastructures checkbox. This feature is GA.

PIPE_FILTER_EXECUTIONS_BY_GIT_EVENTS

This enables users to view both manual executions and those triggered automatically by Git pull requests (PRs) in the My Executions filter on the listing page. Executions triggered by GitHub PRs, as well as manually triggered pipeline executions, will appear in the My Executions list. This feature is in Limited GA.

PIPE_MARK_PARENT_PIPELINE_STATUS_WAITING_AS_CHILD

Enables users to see both the parent and child pipeline statuses as "Waiting" when the child pipeline is in a wait step during pipeline chaining, instead of having the parent pipeline show as Running while the child shows as Waiting. This feature is in Limited GA.

CDS_LIST_REPO_V2

Enables users to search for repositories with infinite scroll support in a specific connector. By entering any keyword, related repositories will be displayed. If the desired repository is not found, users can also add it manually. This feature is in Limited GA.

ENV_GROUP_DEPLOYMENTS_IN_SERIAL

Enables users to use the serial deployment of environment groups. This feature is in Limited GA.

CDS_DISABLE_FALLBACK_EXPRESSION_ENGINE

Enables users to leverage the updated expression resolution fallback logic, which now calls the fallback more effectively. This feature is in Limited GA.

GITOPS_GET_APP_DETAILS_STEP

Enables users to fetch the details and status of their application. This feature is in Limited GA.

CDS_HELM_STEADY_STATE_CHECK_1_16

Allow users leveraging Kubernetes version 1.16 or later to perform steady state check for Helm deployments. This feature is in Limited GA.

OPA_PIPELINE_GOVERNANCE

Enables Policy as code for a Harness account. This feature is GA.

NG_PIPELINE_TEMPLATE

Enables Harness templates. This feature is Limited GA.

OPA_GIT_GOVERNANCE

Store and fetch your OPA policies in Git.. This feature is Limited GA.

NG_CUSTOM_STAGE

Enables theCustom stage for use in a pipeline. This feature is GA.

NG_GIT_EXPERIENCE

Enables Harness Git Experience for a Harness account. Users can manage their Pipeline, Templates, Input Sets, Feature Flags via Git. This feature is GA.

CDP_USE_OLD_GIT_SYNC

Enables the previous, deprecated version of Git Experience. This flag is only enabled for customers who have not migrated over to Harness Git Experience.

CDS_DISABLE_HELM_REPO_YAML_CACHE

Disables Helm repository caching on the Harness Delegate. This should only be enabled if users are experiencing failures with Harness Delegate failing to fetch Helm Charts. Caching could be the source of the issue. This Feature is in Beta.

CD_GIT_WEBHOOK_POLLING

Enables configurable polling for GitHub Webhooks This allows users to set polling interval for Harness Delegate to poll your GitHub instance. This feature is in Limited GA.

CDS_DISABLE_WINRM_COMMAND_ENCODING_NG

Prevents the encoding of WinRM commands. By default Harness encodes the winrm commands we run on hosts. User's can disable this behavior via this feature flag. This feature is in Limited GA.

CDS_TERRAFORM_S3_SUPPORT

Enables AWS S3 for Terraform plan storage. This feature flag is Limited GA.

CDP_USE_K8S_DECLARATIVE_ROLLBACK

Enables the declarative rollback behavior for services. This feature is in Beta.

CDS_K8S_SOCKET_CAPABILITY_CHECK_NG

Replaces the HTTP capability check for the Kubernetes connector with socket capability. This feature is in Beta.

PIE_USE_SECRET_FUNCTOR_WITH_RBAC

Performs RBAC check on secrets when used in pipeline execution. This feature is in Beta.

CDS_GIT_CONFIG_FILES

Enables config files to be managed in Git.

PIE_GITX_OAUTH

Uses users' OAuth credentials to fetch and commit in Git. This feature is in Limited GA.

PIE_MULTISELECT_AND_COMMA_IN_ALLOWED_VALUES

CDS_SUPPORT_HPA_AND_PDB_NG

Enables PDB and HPA tracking as managed resources by Harness. This feature is in Limited GA.

CDS_SSH_SSHJ

Enables a library upgrade for SSH Deployments to use newer algorithms of SSH to connect to hosts. All Delegates on 803xx Release will have the new upgraded library. This feature is Limited GA.

CDS_SSH_CLIENT

Enables a library upgrade for SSH Deployments to use newer algorithms of SSH to connect to hosts. All Delegates on 803xx Release will have the new upgraded library. This feature is Limited GA.

CDS_SERVICE_OVERRIDES_2_0

Enables overrides v2 experience. This feature is in Beta.

CDS_HELM_STEADY_STATE_CHECK_1_16_V2_NG

Enables steady state check for Helm deployments on Kubernetes clusters using 1.16 or higher. This feature is in Beta.

CDS_RESOLVE_OBJECTS_VIA_JSON_SELECT

Support resolution of objects via the JSON Select Command in the HTTP step. This feature is in Beta.

CDS_ENABLE_LOAD_FROM_CACHE_FOR_RETRY_FORM

Enables a load from cache option on pipeline execution retry form. This feature is in Beta.

CDS_RECONFIGURE_JIRA_APPROVAL_TIMEOUT

Reduces timeout for Jira from 5 minutes to 1 minute and allows pausing of approval. This feature is in Beta.

CDS_NG_SERVICE_PRINCIPAL_FOR_CUSTOM_WEBHOOK

Makes authenticated custom Webhook calls use the service principal instead of the principal inherited from the API key. This feature is in Beta.

OPA_AIDA_WIDGET

Enables Harness AI for OPA. This feature is in Beta.

PIE_SIMPLIFY_LOG_BASE_KEY

Reduces the length of the log base key. This feature is in Beta.

This feature requires delegate version 23.10.81010 or later.

After enabling this feature flag, you must re-run your pipelines to apply the change.

For more information, go to Download execution logs.

PIE_ASYNC_FILTER_CREATION

Sets pipeline CRUD calls to filter creation asynchronously. This feature is in Beta.

CDS_CONTAINER_STEP_GROUP_RUN_AS_USER_AND_PRIVILEGED_FIX

Enable this feature if you want updated logic for permissions inheritance between steps and their step groups. To learn more go to Step Group Inheritance Logic. This is a Beta feature.

CV_MONITORED_SERVICE_TEMPLATIZATION

Enable this feature if you want to select a monitored service template as a runtime input. To learn more, go to Select a monitored service template during runtime. This is a Beta feature.

CDS_ASYNC_EXECUTABLE_USE_SELECTORS

When enabled the delegate selector priorities are correctly handled in Helm Blue/Green and Canary Deployment steps. This is a Beta feature.

CDS_NAV_MODULE_VISIBILITY

When enabled Admin users can hide unsubscribed modules from the sidebar, ensuring only subscribed modules are visible to team members. This helps streamline the user experience and prevents access to steps or features from unsubscribed modules. This is a Beta feature.

GITOPS_FILTER_PANE_ENABLED

When enabled, GitOps users can create and save application filters in the GitOps Applications page. This is a Beta feature

FF_PIE_SET_ADVISORS_PROCESSED

When enabled the calculation of <+stage.CurrentStatus> exclude steps where the failure strategy has not yet been triggered. This ensures that steps are not prematurely skipped due to transient failure states, resulting in more reliable execution. This is a Beta feature.

CDS_EXECUTION_LIST_FILTERS

Enable this feature to improve filter UI on the execution list view. Use the new UI to add filter parameters, make custom filters, and save them, easier than before. This is a Beta feature.

CDS_AWS_LAMBDA_ROLLBACK_V2

When enabled, users can deploy Lambda artifacts larger than 50 MB stored in S3 This is a Beta feature.

CDS_GITLAB_TRIGGER_TAG_EVENT

When enabled, u​sers can trigger pipelines in GitLab upon the creation or pushing of tags. This is a Beta feature.

CDS_INCLUDE_EMPTY_VALUE

When enabled, this will allow empty values to be accepted as an allowed value for runtime inputs. This is a Beta feature.

PIPE_FIX_RESOURCE_RESTRAINTS_FOR_RETRY_STEPS

When enabled, this flag ensures that the existing resourceRestraintInstance is reused when a queue step is retried to fix an issue where multiple resource restraints were created for a single queue step. This is a Beta fix

CDC_SERVICE_DASHBOARD_REVAMP_NG

Adds a Metrics tab to the individual service dashboard, showing deployments, failure rate, deployment frequency, active service instances, and the underlying environment and infrastructure over a selected period. This feature is in Limited GA.

CDP_USE_K8S_DECLARATIVE_ROLLBACK_NG

Enables declarative rollback for Kubernetes deployments. This feature is in Limited GA.

CDS_AIDA_SUPPORT_DEFLECTION

Enables AI-assisted support deflection (AIDA). This feature is in Limited GA.

CDS_ALLOW_ACTIVE_FREEZE_EDIT

Editing active freeze windows through the API is blocked by default. Enable this flag to restore the previous behavior that allowed active freeze windows to be edited through the API. This feature is in Limited GA.

CDS_ARTIFACTORY_OIDC_AUTHENTICATION

Adds OIDC authentication to the Artifactory connector, enabling credential-free federated authentication with JFrog Artifactory using short-lived JWT tokens. This feature is in Limited GA.

CDS_ASG_FIX_LIFECYCLE_HOOKS_ORDER

Fixes a race condition where Auto Scaling Group (ASG) instances could launch before lifecycle hooks were added, causing inconsistent deployment behavior. This feature is in Limited GA.

CDS_ASG_SKIP_INSTANCE_HEALTH_CHECK_BEFORE_INSTANCE_REFRESH

Fixes issues that occurred while skipping health checks for ASG instances before an instance refresh. This feature is in Limited GA.

CDS_AUTO_APPROVAL

Enables automatic approval for pipeline approval steps. This feature is in Limited GA.

CDS_AWS_STS_NON_DEFAULT_REGION

Fixes an issue where AWS connectors using OIDC authentication failed to validate in non-default regions such as af-south-1 (Africa South 1). This feature is in Limited GA.

CDS_AZURE_CONTAINER_APPS

Enables deployment to Azure Container Apps directly from Harness CD, with canary deployments, progressive traffic shifting, automatic rollback, and OIDC or key-based authentication. This feature is in Limited GA.

CDS_CONTAINER_STEP_GROUP_REJECT_NESTED_INFRA

Enables backend validation to reject invalid YAML configurations where a containerized step group contains a nested step group as a container or includes a run step inside a nested step group, matching frontend validation restrictions. This feature is in Limited GA.

CDS_CONTAINER_STEP_GROUP_STAGE_TIMEOUT

Enables adding Approval steps inside Container Step Groups in CD pipelines, and automatically extends pod TTL when the stage timeout exceeds 24 hours. This feature is in Limited GA.

CDS_CONTAINER_STEP_USE_STAGE_IDENTIFIER

Fixes intermittent failures of the Wiz security scanning step in containerized step groups by setting the StageId to the stage name instead of a UUID. This feature is in Limited GA.

CDS_CUSTOMIZE_PIPELINE_TTL

Enables a customizable retention period (TTL) for pipeline cache entities. This feature is in Limited GA.

CDS_CV_DYNATRACE_GRAIL_LOGS_ENABLED

Adds support for Dynatrace Grail Logs as a health source for deployment verification. This feature is in Limited GA.

CDS_CV_HEALTH_SOURCES_ENABLED

Enables Health Sources V2 and the Config Agent flow for Datadog metric and log health sources in Continuous Verification (AI Verify). This feature is in Limited GA.

CDS_CV_MS_GITX

Enables storing monitored services in Git using GitX, adding version control and code review workflows for verification configurations. This feature is in Limited GA.

CDS_CV_SUB_TASK_CUSTOM_WEBHOOK_NOTIFICATIONS_ENABLED

Adds custom webhook notifications for Continuous Verification sub-tasks, providing real-time updates on data collection, analysis, and verification status with correlation IDs. This feature is in Limited GA.

CDS_DISABLE_CONNECTOR_PT_CREATION

Fixes an issue where editing a connector reset the Heartbeat Perpetual Task; the Perpetual Task is now properly deleted during connector edits. This feature is in Limited GA.

CDS_DISABLE_FABRIC8_NG

Fixes pipeline failures that occurred when Fabric8 was disabled through this flag. This feature is in Limited GA.

CDS_ECS_BG_VALIDATION

Enables blue-green validation for Amazon ECS deployments. This feature is in Limited GA.

CDS_ECS_SCHEDULED_ACTIONS

Adds support for ECS Scheduled Actions as a new manifest type (EcsScheduledActionDefinition) in ECS service deployments, enabling time-based auto-scaling policies. This feature is in Limited GA.

CDS_ECS_SKIP_APPLICATION_SCALING

Adds a Skip application auto scaling option to ECS Rolling deployments, letting you manage auto-scaling externally and avoid AWS API rate limits. Requires delegate version 26.05.89205 or later. This feature is in Limited GA.

CDS_ENABLE_INFRA_HOST_GROUPS

Adds support for Host Groups in Physical Data Center (PDC) WinRM deployments, letting you assign independent WinRM credentials to different groups of hosts within a single infrastructure definition. This feature is in Limited GA.

CDS_ENABLE_PIPELINE_SCOPED_OIDC_SUB

Fixes an issue where the OIDC sub claim did not include the pipeline ID for containerized step group executions. This feature is in Limited GA.

CDS_ENABLE_SERVICE_ON_RUN_OPA_EVAL

Enables selecting the Service entity for both On Run and On Save events when creating an OPA policy set. This feature is in Limited GA.

CDS_ENABLE_VM_CONTAINER_STEP_GROUP_INFRA

Adds support for VM infrastructure in containerized step groups, letting you run supported CD steps on Linux VMs instead of Kubernetes clusters. This feature is in Limited GA.

CDS_ENV_LISTING_RBAC_IMPROVEMENT

Fixes an issue where service accounts with view permission were unable to list project environments. This feature is in Limited GA.

CDS_ESCAPE_ENV_VARS_FOR_WINRM_KERBEROS_NG

Fixes WinRM command and artifact download failures caused by improper handling of environment variables containing special or illegal XML characters (for example, \, $) when using Kerberos authentication. This feature is in Limited GA.

CDS_GITOPS_DELEGATE_USE_SCM_FOR_COMMIT

Optimizes the performance of the Update Release Repo and Merge PR steps to reduce execution time for large repositories. This feature is in Limited GA.

CDS_GITOPS_ENABLE_ENV_PROPAGATION_UX

Fixes an issue where environment propagation between stages in GitOps PR pipelines failed with validation errors. This feature is in Limited GA.

CDS_GITOPS_SECRET_RESOLUTION_ENABLED

Enables Harness secret expressions (<+secrets.getValue()>) directly in Kubernetes manifests, resolving and decrypting secrets during manifest rendering for Kubernetes Secret objects. Also lets you reference Harness secrets for GitOps cluster credentials when you register a cluster. This feature is in Limited GA.

CDS_HELM_BG_STRATEGY

Adds native support for Canary and Blue-Green deployment strategies with Helm chart deployments. This feature is in Limited GA.

CDS_HELM_MULTIPLE_MANIFEST_SUPPORT_NG

Enables configuring multiple Helm charts in service manifests and migrating services with Helm charts from FirstGen to NextGen, providing feature parity with Harness FirstGen. This feature is in Limited GA.

CDS_HTTP_STEP_NG_CERTIFICATE

Lets you select secrets for a valid TLS certificate and key in the HTTP step for TLS connections. This feature is in Limited GA.

CDS_K8S_PATCH_STEP_NG

Adds a Patch step for Kubernetes deployments to modify specific resources or workloads without affecting other fields, providing parity with the Spinnaker Kubernetes Patch stage. This feature is in Limited GA.

CDS_MANUAL_INTERVENTION_CUSTOM_ACTIONS

Lets pipeline designers customize which actions (for example, Retry, Rollback) are available to the executor for Manual Intervention failure strategies. This feature is in Limited GA.

CDS_NG_CONFIG_FILE_EXPRESSION

Enables the use of Harness expressions in config files. This feature is in Limited GA.

CDS_NG_CONVERT_BRANCH_TO_PUSH_WEBHOOK_BITBUCKET_ON_PREM

Makes triggers for on-premises Bitbucket capture branch hook events and convert them, on a best-effort basis, to push hooks so triggers fire on the first push to a new branch. This feature is in Limited GA.

CDS_NG_TRIGGER_SELECTIVE_STAGE_EXECUTION

Enables selective stage execution for pipeline triggers. This feature is in Limited GA.

CDS_NOT_ALLOW_READ_ONLY_SECRET_MANAGER_TERRAFORM_TERRAGRUNT_PLAN

Fixes an issue where the Terraform Plan step failed when an account-level (read-only) secret manager was selected and this flag was enabled. This feature is in Limited GA.

CDS_OIDC_AWS_SESSION_TAGS

Adds environment identifiers as session tags in OIDC tokens for AWS connectors, enabling environment-specific IAM policy enforcement for resources and secrets. This feature is in Limited GA.

CDS_OVERRIDES_VARIABLE_NAME_VALIDATIONS

Adds validation for override variable names, rejecting names that begin or end with a space or contain special characters. This is a breaking change for already-saved invalid variable names. This feature is in Limited GA.

CDS_PRESERVE_WINRM_WORKING_DIR_FOR_COMMAND_UNITS

Fixes an issue so that Harness uses the working directory you specify in WinRM script units. This feature is in Limited GA.

CDS_ROLLBACK_IN_STEPGROUP_MANUAL_INTERVENTION

Enhances rollback support so that rolling back a stage through manual intervention on a Run step failure executes the rollback stage action instead of failing. This feature is in Limited GA.

CDS_SAVE_EXECUTION_EXPRESSIONS

Displays the execution context, inputs, and outputs for each step on the Execution Details page to help debug pipeline executions. This feature is in Limited GA.

CDS_SECRET_MANAGER_DELEGATE_SELECTOR_PRECEDENCE

Fixes an issue in multi-account AWS setups so that a secret manager's delegate selector takes precedence over the connector's delegate selector, preserving environment IAM isolation. This feature is in Limited GA.

CDS_SERVICENOW_TICKET_TYPE_V2

Enables version 2 of ServiceNow ticket type support. This feature is in Limited GA.

CDS_SERVICE_AND_INFRA_STEP_DELEGATE_SELECTOR_PRECEDENCE

Fixes delegate selection so that stage-level and pipeline-level delegate selectors take precedence in Service and Infrastructure steps. This feature is in Limited GA.

CDS_SHARED_SESSION_WINRM_NTLM_NG

Adds WinRM session pooling for traditional Windows deployments, reusing idle sessions with matching credentials to save connection setup time. Supports NTLM authentication. This feature is in Limited GA.

CDS_SKIP_CDK_DEPLOY_IF_NO_DIFF

Automatically skips AWS CDK Deploy steps when a preceding CDK Diff step detects no infrastructure changes, reducing deployment time. This feature is in Limited GA.

CDS_SKIP_INVALID_SHA_DIGEST_CHECK

Fixes an issue where artifact image SHA256 validation failed after moving a project to a different organization or account. This feature is in Limited GA.

CDS_STORE_PRUNING_RELEASE_HISTORY_IN_SECRET

Stores Kubernetes release history in Secrets instead of ConfigMaps when pruning is enabled, providing a more secure storage mechanism. This feature is in Limited GA.

CDS_TAS_LOGIN_OPTIMIZATION

Fixes an issue where TAS rolling deployments failed for newly created apps with a "No API endpoint set" error. Requires delegate version 859xx or later. This feature is in Limited GA.

CDS_USE_CACHED_REPOSITORY_SUFFIX

Fixes artifact fetching from JFrog Artifactory Edge nodes by falling back to transitive search queries when standard queries return no results. This feature is in Limited GA.

GITOPS_AGENT_METRICS_PORT

Fixes an issue where the GitOps agent metrics server did not initialize correctly, ensuring the correct metrics port is set when metrics are enabled. Requires gitops-helm chart 1.1.16 (or 1.3.5 for gitops-helm-byoa). This feature is in Limited GA.

GITOPS_APPLICATIONSET_FIRST_CLASS_SUPPORT

Adds first-class support for ApplicationSets, providing a scalable solution for multi-environment and multi-cluster GitOps deployments. This feature is in Limited GA.

GITOPS_BULK_ACTIONS_ENABLED

Adds Bulk Sync and Refresh buttons on the applications page so GitOps applications can be synced and refreshed in bulk. This feature is in Limited GA.

GITOPS_RESOURCE_CLIENT_CONNECT_TIMEOUT_SECONDS

Makes the connect timeout for GitOps app refresh calls configurable (for Self-Managed Platform customers, through the ng-manager override). This feature is in Limited GA.

GITOPS_RESOURCE_CLIENT_READ_TIMEOUT_SECONDS

Makes the read timeout for GitOps app refresh calls configurable (for Self-Managed Platform customers, through the ng-manager override). This feature is in Limited GA.

NG_DEPLOYMENT_FREEZE_OVERRIDE

Fixes an issue where triggers failed an RBAC permission check when the deployment freeze override was enabled. This feature is in Limited GA.

NG_OPTIMIZE_FETCH_FILES_KUSTOMIZE

Optimizes fetching of Kustomize manifests for large repositories, adding an Optimized Kustomize Manifest Collection option. This feature is in Limited GA.

NG_SVC_ENV_REDESIGN

Enables the redesigned services and environments experience. This feature is in Limited GA.

OPA_ENABLE_CANARY_AI

Enhances Harness AI for OPA policies with the unified Harness AI agent, offering more accurate, context-aware policy generation and plain-language descriptions of existing policies. This feature is in Limited GA.

PIE_CONTAINER_STEP_ABORT_USE_UPSERT

Fixes an issue where container steps could get stuck when a ZTS denial occurred. This feature is in Limited GA.

PIE_FLEXIBLE_TEMPLATES

Fixes visibility of the Edit (three-dots) button on the template details tab when using long template names. This feature is in Limited GA.

PIE_GITX_EVALUATE_ENCRYPTED_CAPABILITIES

Works with CDS_SECRET_MANAGER_DELEGATE_SELECTOR_PRECEDENCE to fix AWS Secrets Manager connector validation so the secret manager's delegate selector takes precedence, preserving environment IAM isolation. This feature is in Limited GA.

PIE_NG_BATCH_GET_TEMPLATES

Fixes an issue where templates could not be fetched from different repositories associated with the same SCM connector. This feature is in Limited GA.

PIE_PROCESS_TRIGGER_SEQUENTIALLY

Triggers a Git sync before executing associated triggers so pipelines run with the latest Git-synced configurations. This feature is in Limited GA.

PIE_USE_LEGACY_GIT_ENTITY_INFO

Fixes template resolution failures during pipeline retry when the template is stored in a non-default Git branch. This is an inverted flag: disable it to apply the fix. This feature is in Limited GA.

PIPE_ABORT_ONLY_TRIGGERED_BY_SAME_TRIGGER

Fixes an issue so that a trigger only aborts executions started by the same trigger. This feature is in Limited GA.

PIPE_BULK_RECONCILIATION

Adds bulk reconciliation of templates, letting you apply runtime input changes across multiple entities (such as stages or pipelines) in a single action. This feature is in Limited GA.

PIPE_CACHE_CURRENT_STATUS

Fixes incorrect failure strategy behavior where leaf steps skipped their immediate parent step group when updating cached status. This feature is in Limited GA.

PIPE_CRON_TRIGGER_AND_SEMANTICS

Adds AND semantics to Cron triggers so that both date-range and day-of-week conditions must be satisfied simultaneously for complex scheduling. This feature is in Limited GA.

PIPE_DISABLE_DEFAULT_STORE_TYPE_TO_INLINE_FOR_INPUT_SET_CREATE_CHECK

Fixes an issue where users were unable to create overlay input sets due to an incorrect store type validation error. This feature is in Limited GA.

PIPE_DISABLE_OPA_GITCONFIG_NEW_BRANCH_FIX

Fixes an issue where pipelines no longer sent Git configuration to Policy as Code. This feature is in Limited GA.

PIPE_DISABLE_PARENT_REPO_NAME_CONTEXT_POPULATION_FOR_TEMPLATE

Fixes an issue where parentEntityRepo was incorrectly set to the template repo instead of the pipeline repo. This feature is in Limited GA.

PIPE_DISABLE_PIPELINE_CHAINING_FOR_FREE_TIER

Enables gradual enforcement of pipeline chaining limits for the free tier without disrupting existing pipelines. This feature is in Limited GA.

PIPE_DISABLE_TEMPLATE_STABLE_VERSION_RACE_CONDITION_FIX

Fixes an issue where account-level templates displayed duplicate cards and incorrectly marked multiple versions as Stable, preventing deletion through the UI. This feature is in Limited GA.

PIPE_DISABLE_THROWING_ENGINE_EXPRESSION_EVALUATION_EXCEPTION

Improves the "Unable to get secret information" error message to include the original secret name and scope so users can identify the missing or misconfigured secret. This feature is in Limited GA.

PIPE_DYNAMIC_STAGE_EXECUTION

Adds a new Dynamic Stage type that imports and executes pipeline YAML within a stage, where the YAML can be generated at runtime in a previous stage or provided directly. This feature is in Limited GA.

PIPE_ENABLE_BARRIER_STEPS_SETUP_OPTIMIZATION

Fixes an issue where pipelines with parallel stages could hang if a stage was skipped, causing barrier steps to never complete. This feature is in Limited GA.

PIPE_ENABLE_DEPENDENCY_BASED_EXECUTION

Adds support for DAG (Directed Acyclic Graph) pipelines, letting you define explicit stage dependencies through the dependsOn field so that independent execution paths progress as soon as their dependencies finish. This feature is in Beta.

PIPE_ENABLE_GITLAB_ON_PREM_FLOW

Adds support for configuring OAuth for self-hosted GitLab providers. Requires Harness Delegate version 843xx or later. This feature is in Limited GA.

PIPE_ENABLE_QUEUE_BASED_PLAN_CREATION_FOR_TRIGGER_EXECUTIONS

Enables queue-based plan creation for trigger executions, used with Project-Level Pipeline Execution Concurrency. This feature is in Limited GA.

PIPE_ENABLE_TRIGGER_FAILED_NOTIFICATION

Adds notifications for trigger failures, alerting users when a trigger fails to start a pipeline execution. This feature is in Limited GA.

PIPE_GITX_DISABLE_REPO_URL_FOR_GIT_CACHE

Uses the repository URL (repoURL) to perform cache lookups through the Git cache fetch method. This feature is in Limited GA.

PIPE_HONOR_PIPELINE_SDK_PRIORITY_IN_EXECUTION_URL

Fixes an issue where execution links incorrectly redirected to the IDP view in the Harness UI. This feature is in Limited GA.

PIPE_INSERT_STAGE_EXTENDED_SUPPORT

Fixes inconsistent behavior of the Insert Stage functionality. This feature is in Limited GA.

PIPE_PIPELINE_STAGE_PIPELINE_TEMPLATE

Fixes an issue where users were unable to create a template from a pipeline. This feature is in Limited GA.

PIPE_QUEUED_PIPELINE_OBSERVABILITY

Adds an Executions Management page for account-level visibility into queued pipeline executions, with queue positions, filtering by organization or project, and individual or bulk cancellation. This feature is in Limited GA.

PIPE_SHOW_ALL_EXECUTIONS_ON_ACCOUNT_OVERVIEW_PAGE

Shows all pipeline executions in the notification section regardless of module type (CI, CD, and so on), not only executions containing a CD stage. This feature is in Limited GA.

PIPE_SKIP_EXECUTE_WHEN_CONDITION_ON_RETRY_STEP

Fixes an issue so that a step's When condition is re-evaluated on each retry attempt, preventing incorrect execution after an initial evaluation failure. This feature is in Limited GA.

PIPE_TEMPLATE_LABELS_FEATURE

Adds template labels for referencing template versions using semantic names instead of fixed version numbers. This feature is in Limited GA.

PIPE_TRIGGER_SCM_FETCH_THROW_EXCEPTION

Requires PR triggers to use a Git connector with API access enabled; pipeline executions fail with an error if the connector does not have API access. This feature is in Limited GA.

PIPE_USE_DYNAMIC_MODULE_TYPE_IN_BUILD_DETAILS_URL

Fixes an issue where the execution URL in Git status checks from Custom stages always pointed to a CI module path, showing a blank page for accounts without a CI license. This feature is in Limited GA.

PIPE_USE_ENV_REF_BRANCH_IN_SERVICE_OVERRIDE_FOR_INPUTSET_TRIGGER

Improves the misleading error message shown during environment branch selection in service overrides when using InputSet triggers. This feature is in Limited GA.

PIPE_USE_PIPELINE_IDENTIFIER_IN_AUDIT_LOGS

Uses the pipeline identifier in audit logs. If you enable this flag, update your integration points to accommodate the change. This feature is in Limited GA.

PL_GCP_OIDC_AUTHENTICATION

Adds support for custom attributes for OIDC with the GCP connector. This feature is in Limited GA.

SPG_DISABLE_CUSTOM_WEBHOOK_V3_URL

Lets you continue using the previous custom webhook trigger API (v2) instead of the new /v3 token-based API. This feature is in Limited GA.

CDS_AGENT_RUNTIME_DEPLOYMENT

Enables AI agent deployments as a first-class deployment type, so you can deploy an Agent Service to AWS Bedrock AgentCore or Google Vertex Agent Runtime through the standard CD environment, infrastructure, and pipeline model. This feature is in Beta.

CDS_CLEAN_NOTIFICATION_EVENT_TYPE

Fixes an issue where the notification event type intermittently contained infrastructure metadata instead of the event type in notification templates. The event type now resolves to the type alone, with a separate event details value for descriptive information. This feature is in Beta.

CDS_CV_INPUT_OUTPUT_VARIABLES_ENABLED

Enables the customVerificationStartTime configurable property in the AI Verify (v1) step, so you can shift the start of the verification window to an earlier timestamp. This feature is in Beta.

CDS_CV_PER_METRIC_SENSITIVITY

Enables per-metric sensitivity override in the Verify step, so you can set the sensitivity (High, Medium, or Low) individually per metric instead of applying one setting to every metric in a health source. This feature is in Beta.

CDS_USE_METADATA_FOR_CUSTOM_DEPLOYMENT_LIST

Optimizes Custom Deployment service and infrastructure list APIs by persisting the template version label and reference directly in entity metadata instead of fetching and parsing YAML from Git on every request. This significantly improves list performance for accounts with many remote Custom Deployment entities. This feature is in Limited GA.

PIPE_ENABLE_OPA_GOVERNANCE_FOR_AUTO_CREATION, PIPE_OPA_GITX_ENFORCEMENT, CDS_OPA_GOVERNANCE_FOR_WEBHOOK

Enforces onSave OPA policies on Git-backed entities, so a change committed directly to Git to a pipeline, template, service, environment, infrastructure definition, or override is evaluated against the onSave policy and blocks execution when the most recent commit fails the check. For pipelines and templates, execution is blocked at the pipeline level. For CD entities, the violation is surfaced on the entity detail page and execution is blocked at the step level when the entity is referenced. Go to Enforce onSave policies on Git-backed entities to configure. This feature is in Beta.

PIPE_ENFORCE_TRIGGER_EXECUTOR_IDENTITY

Enables a trigger executor identity, so a pipeline started by a trigger runs with an associated user or service account and its RBAC permissions instead of the Harness system principal. This feature is in Beta.

PIPE_GITX_FORCE_REFRESH

Enables on-demand refresh of the Git cache for remote entities through the Reload from Git option or the refresh API, without waiting for a webhook. Refreshing an entity also reloads the caches of its referenced entities. This feature is in Beta.

PIPE_GITX_RATE_LIMITS_API, PIPE_GITX_WEBHOOK_HEALTH_PER_REPO

Enables the Observability views on the Git Experience Webhooks monitoring page, which monitor repository synchronization health and Git provider API rate-limit consumption. This feature is in Beta.

PIPE_MULTILINE_VARIABLE_INPUT

Enables multi-line string input for custom variables, so the value field for a pipeline-scoped or stage-scoped string variable becomes a resizable text area. This feature is in Beta.

PIPE_TEMPLATE_OVERRIDES

Enables template overrides, so a template owner can allow specific advanced settings to be overridden by callers without editing or duplicating the template. Supported for v0 YAML step, stage, step group, and pipeline templates. This feature is in Beta.

PIPE_USE_COUNTER_BASED_STEP_CONCURRENCY_GATE

Enforces an account-level step concurrency limit that caps the total number of concurrently running steps across all pipeline executions in your account, in addition to the per-execution limit. This feature is in Beta.

PIPE_GRAPH_VIEWPORT_PERSISTENCE

Enables pipeline graphs to open zoomed to fit by default and preserve the selected zoom level per pipeline in the browser for Pipeline Studio and pipeline execution views. This feature is in Beta.

Last updated

Was this helpful?