Skip to main content

What's supported

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 includes a built-in Secret Management feature that enables you to store encrypted secrets, such as access keys, and use them in your Harness connectors and pipelines.

In addition to the built-in Secret Manager, Harness Platform supports the cloud platform secrets management services in the following table.

Provider NameKey Encryption SupportEncrypted Data Stored with HarnessSupport for Referencing Existing Secrets
AWS KMSYesYesNo
AWS Secret ManagerYesNoYes
Hashicorp VaultYesNoYes
Azure Key VaultYesNoYes
Google KMSYesYesNo

For more information, go to Harness Secrets Management overview.

Delegates​

Harness packages and distributes delegates on different types of images. Delegate images are identified by the delegate name. Image types are distinguished by tag.

Delegate-Legacy End of Support (EOS) notice

This is an End of Support (EOS) notice for the Delegate-Legacy image type. This image type reached End of Support (EOS) as of January 31, 2024.

End of Support means the following:

  • Harness Support will no longer accept support requests for the Delegate-Legacy image type in both Harness FirstGen and Harness NextGen (including Harness Self-Managed Enterprise Edition (SMP)).
  • Security fixes will still be addressed.
  • Product defects will not be addressed.

Follow the below steps to upgrade Delegate-Legacy to Delegate image

  • Download new yaml from Harness by keeping the same name as the previous delegate
  • Check if the existing delegate has any tags/selector, if yes then add them in DELEGATE_TAGS
  • Compare the permissions given to the legacy delegate in their yaml and give the same permissions to new delegates
  • Check if custom image is used, if yes then build a new image with immutable delegate as base image and override the account setting to point to that image
  • Ensure that auto upgrade is enabled for Kubernetes delegates
  • Our delegate yaml ships with default HPA of min and max replicas to be 1, adjust the desired number of replicas in HPA
  • Deploy the new yaml and see new replicas coming under the same delegate
  • Scale down the old stateful set and verify that everything is correct
Image typeImage tagImage description
DELEGATEyy.mm.xxxxxThe release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform.
DELEGATE-MINIMALyy.mm.xxxxx.minimalThe minimal tag is appended to the release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform.
DELEGATE-LEGACYlatestDelegate that auto upgrades with no flexibility to turn off auto upgrade (DEPRECATED)

AuthN​

The following table lists the supported Authentication features and various ways to authenticate users. Users in Administrator groups can use Authentication Settings to restrict access to an organization's Harness account. The options you choose apply to all of your account's users.

For more information, go to Authentication overview.

SSO TypeSSO ProvidersAuthentication SupportedAuthorization (Group Linking) SupportedSCIM Provisioning
SAML 2.0OktaYesYesYes
Microsoft Entra IDYesYesYes
OthersYesYesNo
OneLoginYesYesYes
OAuth 2.0GithubYesNoN/A
GitLabYesNoN/A
BitbucketYesNoN/A
GoogleYesNoN/A
AzureYesNoN/A
LinkedInYesNoN/A
LDAP (Delegate connectivity needed)Active DirectoryComing soonComing soonN/A
Open LDAPComing soonComing soonN/A
Oracle LDAPComing soonComing soonN/A

Notifications​

Git experience​

Harness Git Experience allows you to store your resource configurations, such as pipelines and input sets, in Git.

Supported Git providers for Harness Git Sync include:

  • GitHub
  • Bitbucket Cloud
  • Bitbucket Server
  • Azure Repos
  • GitLab

You can save the following Harness resources (entities) in Git using Harness Git Experience:

  • Pipelines
  • Input sets
  • Templates
  • Services
  • Environments
  • Infrastructure Definitions
info

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:

ResourcesAccountOrgProject
PipelineNoNoYes
ServicesYesYesYes
EnvironmentsYesYesYes
Git ManagementNoNoYes
ConnectorsYesYesYes
SecretsYesYesYes
SMTP ConfigurationYesNoNo
TemplatesYesYesYes
Audit TrailYesYesYes
DelegatesYesYesYes
GovernanceYesYesYes
Kubernetes

  • Overview:

  • 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)
      • Subscription Id
      • Principal and Service Account
      • GovCloud Support
    • 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:
      • 1.16
      • 1.28.7
      • 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 - 1.24.3
      • Harness has certified versions 1.25, 1.26, 1.27, and 1.28.7 of kubectl. You must install the respective client version of the delegate for Harness to leverage it.
    • Tooling:
      • OpenShift - oc client binary
      • Kustomize - kustomize binary
      • Helm - Helm 3.12 and 2.8 binary.
      • Helm 3.8 can be supported via feature flag.

  • Limitations:

    • Helm:
      • Helm Hooks are not supported for this swimlane. Harness manages and orchestrates the manifests and their release.
      • 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

For details on other tools and versions included in Harness, see Delegate-required SDKs.

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.

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)
      • Subscription ID
      • Principal and Service Account
      • GovCloud Support
    • 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: 2.8 - 3.8
    • 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 helm client 3.12.
    • Tooling:
      • OpenShift - oc client binary
      • Kustomize - kustomize binary
      • Helm - Helm 3.12 & 2.8 binary. Helm 3.8 can be supported via feature flag.
  • Limitations:
    • Helm 2 is deprecated so there is limited support for Helm 2.
    • Helm 3 is now 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
      • Harness Code Repository
    • 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)
  • Overview:
  • 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
  • Overview:
  • 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)
Spot Instances
  • Overview:
  • 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 1.x
      • serverless.com 2.x
      • serverless.com 3.x
  • 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
    • Serverless.com 1.x (limited support). Not all capabilities supported.
    • 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
  • Overview:
  • Supported connectors for deployment:
    • Azure Cloud Connector (AKS Authentication)
      • Subscription Id
      • Principal and Service Account
      • GovCloud Support
  • Supported platforms for deployment:
    • Azure cloud, any Region
  • Versions and tooling support:
    • Azure SDK
  • Limitations:
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:

  • Argo CD version supported: 2.8.2.
  • 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.

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 Development Assistant (AIDA): To support AIDA in Self-Managed Enterprise Edition running in an offline environment, you must add https://harness.openai.azure.com to your allowlist.

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.

FlagDescription
CDS_GOOGLE_CLOUD_RUNAllows users to deploy artifacts to Google Cloud Run. This feature is in Limited GA.
CDS_AZURE_FUNCTIONAllows users to deploy Azure Functions through Harness. This feature is in Limited GA.
CDS_SVC_ENV_DASHBOARD_FOR_ACCOUNT_AND_ORG_LEVELAllows users to do Post-Deployment Rollback for services at both the Account and Organisation levels. This feature is in Limited GA.
CDS_SERVICE_ACCOUNT_SUPPORT_IN_HARNESS_APPROVALEnables users to approve Harness approval requests using the Approval API with a Service Account token. To learn more, refer Using the Approvals API with Service Account Authentication. This feature is in Limited GA.
CDS_AWS_SESSION_TOKEN_SUPPORTEnables users to use JET identity tokens for authentication for AWS connectors. This feature is in Limited GA.
CDS_AWS_EKS_CLUSTER_MANUAL_CONFIGURATIONEnables 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_LIST_BRANCH_V2Enables users to search branches in a repository with infinite scroll and add branches manually when needed. This feature is in Limited GA.
CDS_ENABLE_RAW_MODEThis 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_STORE_TERRAFORM_PLAN_FILE_LOCALLY_ON_DELEGATEEnables users to store the Terraform Plan temporarily on Harness Delegate, avoiding Secrets Manager storage or file size limits. This feature is in Limited GA.
CDS_MARK_PIPELINE_AS_FAILUREEnables users to mark a running pipeline as failed, triggering failure strategies for all executing stages. This feature is in Limited GA.
CDS_AUTH_CHECK_IN_WEBHOOK_DETAILS_ENDPOINTSEnables 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_MIGRATIONEnables 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_PERMISSIONEnables users to control Abort permission separately from other pipeline execute functions. This Feature is in Beta.
CDS_REMOVE_CONNECTOR_HEARTBEATEnables users to set Pre Flight Check as the default for pipeline execution. This feature is in Limited GA.
PL_GCP_OIDC_AUTHENTICATIONEnables user to configure custom attributes for OIDC with the GCP connector. This feature is in Limited GA.
CDS_EVENT_BRIDGE_WEBHOOKEnables 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_INPUTEnables 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_REQUESTSEnables users to fetch an artifact version from Nexus during deployment. This feature is in Limited GA.
CDS_EMAIL_USE_DEFAULT_FORMATTINGEnables 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_OUTPUTEnables users to access Kubernetes service and job names in the exported manifest. This feature is in Limited GA.
CDS_K8S_ASYNC_STEP_STRATEGYEnables 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_REFRESHEnable this feature to eliminate downtime during the Auto Scaling Group (ASG) rollback instance refresh. This feature is in Limited GA.
CDS_CF_CLI_ENVIRONMENT_VARIABLE_SUPPORTEnables users to configure CLI environment variables for Tanzu Application Service deployment in the Service and overrides. This feature is in Limited GA.
CDS_ALLOWED_VALUES_DROPDOWN_PDC_HOSTSEnables users to define allowed values in the Select Hosts settings under infrastructure. In the runtime view, a multi-select dropdown will be displayed, allowing users to choose from the predefined allowed values. This feature is GA.
CDS_OVERRIDES_GITXEnables users to manage overrides using Git, with options to store them remotely or inline This feature is in Limited GA.
CDS_MULTI_DEPLOYMENT_ON_FAILUREEnables users to apply failure strategies during multi-service, multi-infrastructure, and matrix deployments. This feature is in Limited GA.
CDS_SERVICE_INFRA_FAILURE_STRATEGYEnables a failure strategy for the service, where the service step will, by default, inherit the failure strategy from the stage. This feature is in Limited GA.
CDS_SPECIFY_INFRASTRUCTURESEnables users to select all the infrastructures in the environment by choosing the All Infrastructures checkbox. This feature is GA.
PIPE_FILTER_EXECUTIONS_BY_GIT_EVENTSThis 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.
CDS_SERVICE_ENV_CLONINGEnables users to clone services across different scopes, such as from one project to another, from a project to an organization, or from an account to a project, as well as across environment scopes. This feature is in Limited GA.
PIPE_MARK_PARENT_PIPELINE_STATUS_WAITING_AS_CHILDEnables 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_V2Enables 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_SERIALEnables users to use the serial deployment of environment groups. This feature is in Limited GA.
PIE_SHOW_ALL_EXECUTIONS_FILTEREnables users to lists all pipeline executions including retired and child executions in the Executions page. This feature is GA.
CDS_DISABLE_FALLBACK_EXPRESSION_ENGINEEnables users to leverage the updated expression resolution fallback logic, which now calls the fallback more effectively. This feature is in Limited GA.
CDS_K8S_PATCH_STEP_NGWe have introduced a Patch step for Kubernetes deployments to make changes to specific resources or workloads in a Kubernetes cluster without affecting other fields. This step helps Spinnaker users migrate to Harness. Spinnaker has a stage type called Kubernetes Patch. This feature flag is Limited GA.
GITOPS_AGENT_HELM_V2Enables you to download a helm-chart file for the Harness GitOps Agent. This feature is GA.
CDS_GITOPS_LABELS_BASED_ACCESS_TO_APPSAllow users to filter applications based on labels while creating a resource group for Gitops application. This feature is in Limited GA.
GITOPS_MULTI_SOURCE_ENABLEDEnables users to support Multi-Source applications with ArgoCD in Harness GitOps. This feature is in Limited GA.
GITOPS_GET_APP_DETAILS_STEPEnables users to fetch the details and status of their application. This feature is in Limited GA.
CDS_HELM_STEADY_STATE_CHECK_1_16Allow users leveraging Kubernetes version 1.16 or later to perform steady state check for Helm deployments. This feature is in Limited GA.
OPA_PIPELINE_GOVERNANCEEnables Policy as code for a Harness account. This feature is GA.
CDS_HELM_VERSION_3_8_0Sets the default version of Helm to 3.8 when using the Harness Helm delegate. This feature is in Limited GA.
NG_PIPELINE_TEMPLATEEnables Harness templates. This feature is Limited GA.
OPA_GIT_GOVERNANCEStore and fetch your OPA policies in Git.. This feature is Limited GA.
NG_CUSTOM_STAGEEnables theCustom stage for use in a pipeline. This feature is GA.
NG_GIT_EXPERIENCEEnables 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_SYNCEnables 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_CACHEDisables 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_POLLINGEnables 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_NGPrevents 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_SUPPORTEnables AWS S3 for Terraform plan storage. This feature flag is Limited GA.
CDP_USE_K8S_DECLARATIVE_ROLLBACKEnables the declarative rollback behavior for services. This feature is in Beta.
CDS_K8S_SOCKET_CAPABILITY_CHECK_NGReplaces the HTTP capability check for the Kubernetes connector with socket capability. This feature is in Beta.
PIE_GET_FILE_CONTENT_ONLYOptimizes the execution flow to fetch only file content for remote entities.
CDS_SERVICE_CONFIG_LAST_STEPAllows users on the last step of manifest/artifact/config files, if these configs are in edit mode. This feature is in Limited GA.
PIE_USE_SECRET_FUNCTOR_WITH_RBACPerforms RBAC check on secrets when used in pipeline execution. This feature is in Beta.
CDS_GIT_CONFIG_FILESEnables config files to be managed in Git.
PIE_GITX_OAUTHUses users' OAuth credentials to fetch and commit in Git. This feature is in Limited GA.
PIE_MULTISELECT_AND_COMMA_IN_ALLOWED_VALUESEnables the ability to choose multiple values from a list of allowed values.
CDS_ARTIFACTS_PRIMARY_IDENTIFIERAllows you to change the expression value for the primary artifact identifier. This feature is in Beta.
CDS_SUPPORT_HPA_AND_PDB_NGEnables PDB and HPA tracking as managed resources by Harness. This feature is in Limited GA.
CDS_SSH_SSHJEnables 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_CLIENTEnables 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.
CD_TRIGGER_CATALOG_API_ENABLEDFetches the list of Trigger options by an API call instead of from the UI.
CDS_SERVICE_OVERRIDES_2_0Enables overrides v2 experience. This feature is in Beta.
CDS_TEMPLATE_ERROR_HANDLINGAdds enhanced error handling for templates by schema validation errors. This feature is in Limited GA.
CDS_HELM_STEADY_STATE_CHECK_1_16_V2_NGEnables steady state check for Helm deployments on Kubernetes clusters using 1.16 or higher. This feature is in Beta.
CDS_AZURE_WEBAPP_LISTING_APP_NAMES_AND_SLOTSEnables users to select Azure WebApps in a drop down for slot deployments. This feature is in Limited GA.
CDS_RESOLVE_OBJECTS_VIA_JSON_SELECTSupport resolution of objects via the JSON Select Command in the HTTP step. This feature is in Beta.
CDS_SUPPORT_EXPRESSION_REMOTE_TERRAFORM_VAR_FILES_NGEnables Harness expressions in remote Terraform var files. This feature is in Beta.
CDS_ENABLE_LOAD_FROM_CACHE_FOR_RETRY_FORMEnables a load from cache option on pipeline execution retry form. This feature is in Beta.
CDS_ENV_PROPAGATIONEnables environment propagation across CD stages. This feature is in Limited GA.
CDS_RECONFIGURE_JIRA_APPROVAL_TIMEOUTReduces 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_WEBHOOKMakes authenticated custom Webhook calls use the service principal instead of the principal inherited from the API key. This feature is in Beta.
CD_MAKE_CD_LICENSE_USAGE_ASYNCEnables CD License Usage dashboards to be asynchronous. This feature is in Beta.
CDS_ENABLE_SHELL_SCRIPT_FILE_REFERENCEEnables the Shell Script step to support scripts from Harness File Store. This feature is in Beta.
CDS_DISABLE_EVALUATE_EXPORT_VARIABLESEnables exporting variables without evaluating them in the Command step. This feature is in Beta.
CD_CONTAINER_STEP_DELEGATE_SELECTORMakes the Container step to respect the delegate selector configured at the pipeline. This feature is in Beta.
CDS_REMOVE_TIME_BUCKET_GAPFILL_QUERYRemoves the usage of time bucket gapfill from CD. This feature is in Beta.
CDS_TERRAGRUNT_USE_UNIQUE_DIRECTORY_BASE_DIR_NGEnables a unique directory to support Terragrunt run-in-parallel. This feature is in Beta.
OPA_AIDA_WIDGETEnables AIDA for OPA. This feature is in Beta.
PIE_SIMPLIFY_LOG_BASE_KEYReduces 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_CREATIONSets pipeline CRUD calls to filter creation asynchronously. This feature is in Beta.
CDS_AWS_OIDC_AUTHENTICATIONEnables the option to connect to AWS with OIDC. Currently, this option is only supported for Kubernetes, Helm, Terraform, ECS, and Cloudformation. This is a Beta feature.
CV_NEWRELIC_NEW_APIEnable this feature if you want to use the NerdGraph API for the NewRelic Health Source. This is a Beta feature.
CDS_CONTAINER_STEP_GROUP_RUN_AS_USER_AND_PRIVILEGED_FIXEnable 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_TEMPLATIZATIONEnable 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.