Add a Service
Services represent your microservices/apps. You define where the artifacts for those services come from, and you define the container specs, configuration variables, and files for those services.
In this topic:
- Before You Begin
- Step 1: Add a Service
- Step 2: Select Deployment Type
- Step 3: Select an Artifact Source
- Container Specs and Manifests
Before You Begin
- Read the Create an Application topic to get an overview of how Harness organizes Services.
- Read the Add a Service topic to understand the process to add a Service to an Application.
- Read Configuration as Code to see how you can quickly configure your Harness Service using your existing YAML in Git.
Step 1: Add a Service to a Harness Application
To add a service, do the following:
- Click Setup, and then click the name of your application. The application entities appear.
- Click Services, and then click Add Service. The Service dialog appears.
- Select a Deployment Type. Each deployment type will set up a Service for its deployment platform. For example, selecting Kubernetes creates a Service with default Kubernetes manifest files.
- Click SUBMIT. The Service Overview appears. In this new Service you will set up artifacts, container specs, and configuration files and variables.
Step 2: Select Deployment Type
There are multiple Service types used in Harness, listed in the Deployment Type field, such as Kubernetes and Helm.
These Service types are discussed in detail in the deployment guides for those platforms. For more information, see Deployments Overview.
Step 3: Add an Artifact Source
Different Service types support different artifact sources, such as Docker or Amazon AMI. For details on different service types and artifact sources, see Service Types and Artifact Sources.
Manually Select an Artifact
You can have Harness pull a list of builds and versions from an Artifact Source. Click Artifact History, and then Manually pull artifact. The Manually Select An Artifact dialog appears.
Select the artifact source in Artifact Stream, and then the artifact build in Artifact.
Container Specs and Manifests
You can use container specifications and manifests to configure a Service. For information on the specs and manifests available for the different Service types, see Deployments Overview.