> 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/continuous-delivery/3.0/deployment-entities/service.md).

# Service

Understand what a Harness service represents and how it fits into a deployment pipeline.

A Harness service represents what you deploy. It holds the artifact reference, the manifests or specifications, configuration files, and service-level variables that describe your application.

Services exist independently of pipelines. You define a service once and reuse it across multiple stages, pipelines, and environments without duplicating configuration.

***

## Service definition <a href="#service-definition" id="service-definition"></a>

Each service has a service definition that specifies the artifact, manifest files, and variables for a given deployment type, such as Kubernetes or Helm. When you add a service to a pipeline stage, you can override any of these values for that specific deployment.

{% hint style="info" %}
**Pre-built artifacts**

Harness Deployments focuses on deploying pre-built artifacts. If you need to build artifacts first, use Harness Builds steps.
{% endhint %}

## Create a service <a href="#create-a-service" id="create-a-service"></a>

In the Harness application, expand **Deployments** in the left navigation and select **Services** to open the list of services for the project.

The services list shows every service in the project, along with its deployment type and when it was created or last modified. Use the search box or **Add filter** to narrow the list, sort by **Last modified**, and use **Columns** to choose which columns appear in the table.

To create a service, select **+ Create service** and complete the following steps.

1. Choose a **Deployment Target**, such as Kubernetes or Helm. Harness uses this to set the service's deployment type.
2. Enter a **Name** for the service, or select the name Harness suggests.
3. Choose a **Storage** option for the service definition. **Inline** stores the manifest and configuration directly on the service.
4. Optionally, select **More options** to add **Metadata**, such as a description and tags.
5. Select **Create**.

Harness creates the service and opens its detail page.

## View and manage a service <a href="#view-and-manage-a-service" id="view-and-manage-a-service"></a>

A service's detail page has two tabs. **Configuration** shows the service name, service ID, deployment type, and when the service was created and last modified, along with its manifests, artifact sources, and variables. **References** shows which pipelines use the service.

To change a service's configuration, select **⋮** (show more actions) on the service's detail page, then select **Edit**. The edit panel lets you update the manifest, add an additional override file, and set the artifact source and sidecar for the deployment type. Under **Advanced**, you can add config files and variables, and under **Metadata**, you can update the description and tags. Select **Apply changes** to save.

You can also select **Clone** or **Delete** from the same **⋮** menu to copy or remove the service.

## Service-level failure handling <a href="#service-level-failure-handling" id="service-level-failure-handling"></a>

You can set a failure strategy directly on a service so that Harness reacts to a failure while resolving the service, before any infrastructure or execution steps run.

Go to [Failure strategy](https://developer.harness.io/continuous-delivery/3.0/deployment-entities/service/failure-strategy.md) to configure `on-failure` rules at the service level.

***

## Next steps

* Go to [Failure strategy](https://developer.harness.io/continuous-delivery/3.0/deployment-entities/service/failure-strategy.md) to configure what happens when service resolution fails.
* Go to [Deployments overview](https://developer.harness.io/continuous-delivery/3.0/new-to-deployments/overview.md) to review how services fit into the overall pipeline model.

{% @harness-feedback/feedback %}
