Configure Service Dependency Step Settings

Updated 2 months ago by Michael Cretzman

If you decide to split your pipeline into multiple stages you need to make sure each stage has access to any dependencies. The Configure Service Dependency step in a Build stage allows you to add the dependencies.

This topic provides settings and permissions for the Configure Service Dependency step.

In this topic:

Name

The unique name for this step.

ID

See Entity Identifier Reference.

Description

Text string.

Container Registry

Harness Connector for the container registry containing the service dependency image, such as DockerHub.

Image

The name of the Docker image.

The image name should include the tag and will default to the latest tag if unspecified.

You can use any Docker image from any Docker registry, including Docker images from private registries.

Example: mysql:5

Privileged

Enable this option to run the container with escalated privileges. This is the equivalent of running a container with the Docker --privileged flag.

Environment Variables

Environment variables injected into the container.

Entry Point

ENTRYPOINT instructions allow you to configure a container that will run as an executable.

You can add commands in Entry Point to override the image ENTRYPOINT. See ENTRYPOINT best practices from Docker.

Commands should be in exec form.

Each command and parameter should be added separately. For example:

For a useful summary of ENTRYPOINT and CMD see Demystifying ENTRYPOINT and CMD in Docker from AWS.

Arguments

Overrides the image CMD.

Each argument should be in exec form.

For example:

For a useful summary of ENTRYPOINT and CMD see Demystifying ENTRYPOINT and CMD in Docker from AWS.

Image Pull Policy

Select an option to set the pull policy for the image.

  • Always: the kubelet queries the container image registry to resolve the name to an image digest every time the kubelet launches a container. If the kubelet encounters an exact digest cached locally, it uses its cached image; otherwise, the kubelet downloads (pulls) the image with the resolved digest, and uses that image to launch the container.
  • If Not Present: the image is pulled only if it is not already present locally.
  • Never: the image is assumed to exist locally. No attempt is made to pull the image.

Run as User

Set the value to specify the user id for all processes in the pod, running in containers. See Set the security context for a pod.

Set container resources

Maximum resources limit values for the resources used by the container at runtime.

Limit Memory

Maximum memory that the container can use.

You can express memory as a plain integer or as a fixed-point number using one of these suffixes: G, M.

You can also use the power-of-two equivalents: Gi, Mi.

Limit CPU

See Resource units in Kubernetes.

Limit the number of cores that the container can use.

Limits for CPU resources are measured in cpu units.

Fractional requests are allowed. The expression 0.1 is equivalent to the expression 100m, that can be read as one hundred millicpu.

Timeout

Timeout for the step. Once the timeout is reached, the step fails, and the Pipeline execution continues.


Please Provide Feedback