> For the complete documentation index, see [llms.txt](https://docs.litwizlabs.ai/wizstudio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.litwizlabs.ai/wizstudio/visual-pipeline-builder/custom-step/properties.md).

# Properties

<figure><img src="/files/MHaRdlgAxROYamutIl9m" alt=""><figcaption></figcaption></figure>

## Step Name

This is the name of the step in the pipeline. It should be unique and accurately reflect the purpose of the step.

{% hint style="info" %}
Only smallcase words seperated with "-" are allowed
{% endhint %}

## Image

Enter the name along with the tag of the Docker image you want to run in the step. e.g. "hello-world:latest"

## Command

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".

## File Name

This is the name of the file that should be executed along with the command. e.g. "main.py"

## Arguments

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.

## Resources

This section allows you to specify the resource requirements for the step. This can include CPU and memory requirements.

### CPUs

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.

{% hint style="info" %}
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`.
{% endhint %}

### Memory

You can express memory as a plain integer or as a fixed-point number using one of these [quantity](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/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:

```shell
128974848, 129e6, 129M,  128974848000m, 123Mi
```

## Node Selector

`Node Selector`is the simplest recommended form of a node selection constraint. You can add the`Node Selector` field to your Pod specification and specify the [node labels](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#built-in-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

Name of the Kubernetes node label to target for scheduling the step on.

### Value

Value of the Kubernetes node label to target for scheduling the step on.