> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/use-artifact-registry/platform-integrations/cd-ar-integrations.md).

# Artifact Registry and Continuous Delivery

Harness Artifact Registry (HAR) integrates with Harness Continuous Delivery (CD) pipelines, enabling you to store, manage, and deploy artifacts across your software delivery lifecycle. This integration provides a unified experience for artifact management and deployment, ensuring traceability from build to production.

***

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

Make sure you have the following:

* **Harness account** with both Artifact Registry and Continuous Delivery modules enabled.
* **Artifacts stored in HAR:** Go to [Create a registry](/artifact-registry/use-artifact-registry/manage-registries/create-registry.md) to set up your registry and push artifacts.
* **CD pipeline:** Go to [CD overview](/continuous-delivery/new-to-continuous-delivery/overview.md) to understand pipeline fundamentals.
* **Kubernetes Cluster connector** (only required for the Containerized Step Group flow described below): Go to [Kubernetes Cluster connector](/harness-ai/use-harness-platform/connectors/cloud-providers/add-a-kubernetes-cluster-connector.md) to add one.

***

### Supported CD swimlanes <a href="#supported-cd-swimlanes" id="supported-cd-swimlanes"></a>

Harness Artifact Registry works with a wide range of CD swimlanes. Go to [CD integrations](/continuous-delivery/new-to-continuous-delivery/cd-integrations.md) to view the complete list of supported swimlanes and artifact types.

***

### Configure CD services with Harness Artifact Registry <a href="#configure-cd-services-with-harness-artifact-registry" id="configure-cd-services-with-harness-artifact-registry"></a>

Once you have artifacts stored in your Harness Artifact Registry, configure your CD services to use HAR as the artifact source:

1. In your CD service configuration, select **Harness Artifact Registry** as the artifact source.
2. Specify the registry and repository details.
3. Define your artifact selection criteria (tags, versions, or latest).

Once configured, your service is ready to be deployed. The CD pipeline automatically fetches artifacts from HAR during execution.

Go to [Use artifacts from Harness Artifact Registry](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/artifact-sources.md#use-artifacts-from-harness-artifact-registry) to follow detailed step-by-step instructions on configuring services.

***

### Deployment workflow <a href="#deployment-workflow" id="deployment-workflow"></a>

Once your CD service is configured with Harness Artifact Registry, the deployment pipeline automatically authenticates with HAR, pulls the specified artifact version, and deploys it to your target environment.

***

### Add a Run step inside a Containerized Step Group <a href="#add-a-run-step-inside-a-containerized-step-group" id="add-a-run-step-inside-a-containerized-step-group"></a>

Reference container images stored in Harness Artifact Registry directly from a CD **Run** step, without a Docker connector. This is available when the Run step is inside a **Step Group** with container-based execution enabled.

1. In your CD pipeline stage, go to **Execution** and add a **Step Group**.
2. In the Step Group configuration, enable **Container based execution**.
3. In **Kubernetes Cluster**, select a Harness Kubernetes Cluster connector for the cluster where the step containers should run.
4. Select **Apply Changes** to save the Step Group configuration.
5. Inside the Step Group, select **+ Add Step** and add a **Run** step.
6. In the Run step, set **Registry Type** to **Artifact Registry**.
7. In **Container Registry**, select the Harness Artifact Registry that hosts the image, and in **Image**, enter the image reference (for example, `myapp:1.2.3`).

{% hint style="info" %}
Choose **Third-Party Artifact Registry** instead when you want to pull the image from an external Docker registry through a Harness Docker connector.
{% endhint %}

Go to [Containerized Step Groups](/continuous-delivery/use-continuous-delivery/cd-building-blocks/cd-steps/containerized-steps/containerized-step-groups.md) to review the full Step Group configuration reference and Kubernetes cluster options.

***

### Benefits of HAR and CD integration <a href="#benefits-of-har-and-cd-integration" id="benefits-of-har-and-cd-integration"></a>

The native integration between HAR and CD provides several advantages:

* **Unified platform experience:** Consistent authentication, permissions, and audit logging across artifact management and deployment workflows.
* **Automated artifact selection:** Configure pipelines to automatically select artifact versions based on tags, labels, or runtime inputs.
* **Security and compliance:** Ensure only approved artifacts are deployed with built-in access controls and audit trails.

***

### Next steps <a href="#next-steps" id="next-steps"></a>

After configuring your CD services with Harness Artifact Registry:

* Go to [CD integrations](/continuous-delivery/new-to-continuous-delivery/cd-integrations.md) to review supported swimlanes and deployment types.
* Go to [Artifact sources in CD services](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/artifact-sources.md#use-artifacts-from-harness-artifact-registry) to configure artifact sources for your pipelines.
* Go to [Artifact Registry best practices](/artifact-registry/3.0/troubleshooting-and-resources/ar-best-practices.md) to optimize your registry configuration.