Harness Services Technical Reference

Updated 3 weeks ago by Michael Cretzman

Harness Services represent your microservices/apps. You define where the artifacts for those microservices come from, and the container specs, configuration variables, and files for those microservices.

See general Harness Service How-tos.

Find deployment platform-specific information for Services in the respective deployment how-tos. See Continuous Deployments.

Harness Service Names

Harness Service names are limited to the following characters:

  • - (dash)
  • _ (underscore)
  • a-z
  • A-Z
  • 0-9
  • space

Don't use target platform naming conventions that don't conform to these characters.

For example, if the target platform allows dots, like my.sample.app, don't use dots in your Harness Service name.

Deployment Type

The list of deployment types Harness supports. This list is growing all the time.

For the latest supported platforms, see Supported Platforms and Technologies.


How did we do?