Properties
Last updated
Last updated
This is the name of the step in the pipeline. It should be unique and accurately reflect the purpose of the step.
Only smallcase words seperated with "-" are allowed
Enter the name along with the tag of the Docker image you want to run in the step. e.g. "hello-world:latest"
This is the command that should be executed when the step is run. It should be a valid command that can be run in a Docker container using the specified image. e.g. "python".
This is the name of the file that should be executed along with the command. e.g. "main.py"
This is a list of arguments that should be passed to the command when it is run. The arguments should be specified as a space-separated list.
This section allows you to specify the resource requirements for the step. This can include CPU and memory requirements.
This specifies the number of CPU cores that should be allocated to the step.
CPU resource is always specified as an absolute amount of resource, never as a relative amount. For example, 500m
CPU represents the roughly same amount of computing power whether that container runs on a single-core, dual-core, or 48-core machine.
Kubernetes doesn't allow you to specify CPU resources with a precision finer than 1m
. Because of this, it's useful to specify CPU units less than 1.0
or 1000m
using the milliCPU form; for example, 5m
rather than 0.005
.
You can express memory as a plain integer or as a fixed-point number using one of these quantity suffixes: E, P, T, G, M, k. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki. For example, the following represent roughly the same value:
Node Selector
is the simplest recommended form of a node selection constraint. You can add theNode Selector
field to your Pod specification and specify the node labels you want the target node to have. Kubernetes only schedules the pod onto nodes that have each of the labels you specify.
Name of the Kubernetes node label to target for scheduling the step on.
Value of the Kubernetes node label to target for scheduling the step on.