Understanding Steps
Steps are the only required objects to create a task, and that makes sense. Steps describe the containers that will run as part of the task. This is where the actual operations to be performed on your inputs happen.
In the YAML file that describes the task, you define steps by adding an array describing the steps and the order they should be performed in.
Each step must have, at a minimum, an image to use. It is also highly recommended to use a command value or a script field. This is because the container's entry point is overwritten with an executable that manages the step execution for Tekton.
A typical Step would also contain a name and would generally look like this:
spec: steps: - image: alpine:3.12 command: - /bin/bash - -c ...