Skip to main content

What's supported

Last updated on

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 FIPSyy.mm.xxxxx-fipsThe 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-MINIMALyy.mm.xxxxx.minimal-fipsThe minimal 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-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:
      • 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 3.12 (default) and 2.8 binary
      • Helm 3.8 supported via feature flag CDS_HELM_VERSION_3_8_0

  • 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
  • 1.30.10
  • 1.31.8
  • 1.33.4

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)
Google Cloud Run
  • Overview:
  • 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
    • Feature currently behind feature flag CDS_GOOGLE_CLOUD_RUN
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 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
  • 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:
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:

  • Argo CD versions supported: 2.8.2 and later (up to 2.12.x).
  • 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_CONTAINER_STEP_DELEGATE_SELECTOR_PRECEDENCEEnable 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_SUPPORTEnables 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_EXECUTIONEnables 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_PIPELINESEnables 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_SPLITEnables 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_CREATIONEnables 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_ENTITYEnables 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_REGISTRATIONEnables 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_FIXEnables 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_ROLLBACKEnables 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_WORKLOADEnables 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_SUPPORTEnables 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_STRATEGYEnables 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_FILTEREnables 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_FLOWEnables 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_TRIGGERSEnables 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.
CDS_UI_ENABLE_DISALLOWED_USER_EMAILS_IN_APPROVAL_STEPEnables users to block specific users from approving steps using Disallowed User Emails. This feature is in Limited GA.
CDS_MANIFEST_HASH_WITH_DECLARATIVE_ROLLBACKEnables users to ensure Kubernetes workloads are redeployed when referenced ConfigMaps or Secrets are updated, even if the deployment spec itself remains unchanged. This is achieved by hashing manifest content under declarative rollback. This feature is in Limited GA.
PIPE_EXECUTION_ID_FILTEREnables 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_TRIGGERSHarness 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_WORKLOADSEnables 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_UPDATESEnables 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.
PIPE_STAGE_NOTIFICATION_ENV_SVCEnables users to include the service name and environment in the subject line of EMAIL notifications, making them searchable and context-rich. This feature is in Limited GA.
CDS_TEXTAREA_FOR_OVERRIDE_VARIABLESHarness now supports viewing full variable values in the Override tab. Users can see and edit entire override values without truncation. This feature is in Limited GA.
CDS_TF_POLICY_EVALUATIONHarness now fetches Terraform Enterprise OPA policy evaluation results and fails the pipeline stage when a policy evaluation fails, ensuring pipelines correctly enforce OPA policy compliance. This feature is in Limited GA.
CDS_AWS_LAMBDA_ECS_TAG_SUPPORTUsers 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_SIMPLIFICATIONImproves 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_TEMPLATESEnables 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_STEPAllows 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_PATHFixes 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_CDKExpands 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_V2Allows 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_SECRETSEnables 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.
CDS_ECS_TRAFFIC_SHIFTIntroduces the ECS Traffic Shifting step to support weighted traffic shifting and Spot deployments, enabling gradual rollout strategies for ECS services with low task counts. This feature is in Limited GA.
CDS_SKIP_HELM_INSTALLEnables Helm deployments with CRDs by supporting helm upgrade --install, allowing resources that already exist outside the namespace to be deployed seamlessly. This feature is in Limited GA.
PIPE_USE_ORIGINAL_YAML_FOR_EXECUTIONEnables 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_OUTPUTFixes rollback handling for user-initiated failures and approval rejections by ensuring rollback strategies execute as expected. This feature is in Limited GA.
CDS_MANIFEST_CONNECTOR_URLEnables users to fetch the Service Manifest source (i.e., Connector URL where the manifest is stored) using the expression <+manifests.MANIFEST_ID.store.connectorUrl>. This feature is in Limited GA
CDS_REMOVE_COMMENTS_FROM_VALUES_YAML_WITH_ESCAPE_CHARACTERSEnables proper handling of special characters in values.yaml by removing control characters such as single (' ), double ("), and backslash (\), preventing pipeline failures.
CDS_ENFORCE_GIT_EXPERIENCEEnables 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_EXTRACTIONEnsures 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_DEPLOYMENTEnables 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_HELM_DELETE_STEPEnables a native Helm Uninstall step in the Deploy stage to uninstall Helm charts. This feature is in Limited GA
CDS_ECS_MONITOR_TASK_STATUSEnables Harness to accurately detect failures in ECS Rolling Deployments. This feature is in Limited GA
PIPE_USE_HARNESS_CODE_FOR_INLINE_ENTITIESSaves inline entities in the Harness Code Repository by default. This feature is in Limited GA
PIPE_DYNAMIC_PIPELINES_EXECUTIONAllows 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_RESOLUTIONIntroduces 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_GITEnables users to import OPA policies directly from Git. This feature is in Limited GA
CDS_GITOPS_OPERATOREnables 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_PARSEREnables 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_V2Enables 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_GROUPSEnables 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_GROUPSEnables 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_LOGSEnables 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_SUPPORTEnsures that overrides from environment configuration YAML are ignored when Override V2 is enabled. This feature is in Limited GA.
CDS_GOOGLE_CLOUD_RUNAllows users to deploy artifacts to Google Cloud Run. 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_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_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_EVENT_BRIDGE_WEBHOOK and CD_TRIGGERS_REFACTOREnables 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_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.
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.
GITOPS_MULTI_SOURCE_ENABLEDEnables users to support Multi-Source applications with Argo CD 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_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.
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_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.
CDS_ASYNC_EXECUTABLE_USE_SELECTORSWhen enabled the delegate selector priorities are correctly handled in Helm Blue/Green and Canary Deployment steps. This is a Beta feature.
CDS_BLUE_GREEN_RESOURCE_FORMAT_FIXWhen enabled it ensure correct resource formatting during Helm Blue-Green deployments. This is a Beta feature.
CDS_NAV_MODULE_VISIBILITYWhen 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_ENABLEDWhen enabled, GitOps users can create and save application filters in the GitOps Applications page. This is a Beta feature
FF_PIE_SET_ADVISORS_PROCESSEDWhen 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_FILTERSEnable 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_EXECUTION_LIST_CARD_VIEWEnable this feature to improve the cards for the execution list view. This allows for other modules data to be displayed in each card on the list. This is a Beta feature
CDS_RECENT_SCOPESWhen enabled, hover over the scope selector to navigate to your five most recent scopes. Clicking the scope selector will continue to be the usual scope selection flow. This is a Beta feature.
CDS_SETTINGS_ACCORDIONWhen enabled, a pop up tile will appear when hovering over Project Settings in the left navigation pane. This is a Beta feature.
CDS_AWS_LAMBDA_ROLLBACK_V2When enabled, users can deploy Lambda artifacts larger than 50 MB stored in S3 This is a Beta feature.
CDS_K8S_TRAFFIC_ROUTE_REWRITE_RULE_SUPPORTWhen enabled, users can define and manage rewrite rules to control traffic routing in Kubernetes traffic routing configuration. This is a Beta feature.
CDS_GITLAB_TRIGGER_TAG_EVENTWhen enabled, u​sers can trigger pipelines in GitLab upon the creation or pushing of tags. This is a Beta feature.
CDS_OPTIONAL_VALUES_YAMLWhen enabled, ​users can utilize an optional checkbox for Kubernetes and Helm deployment types while configuring manifest and overrides. This is a Beta feature.
CDS_INCLUDE_EMPTY_VALUEWhen enabled, this will allow empty values to be accepted as an allowed value for runtime inputs. This is a Beta feature.
CDS_MANIFEST_HASH_WITH_DECLARATIVE_ROLLBACKWhen enabled, this flag enables declarative rollback for changes to solely ConfigMap and Secret object changes. This is a Beta feature
PIPE_FIX_RESOURCE_RESTRAINTS_FOR_RETRY_STEPSWhen 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