Tekton Resource: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
(Created page with "=Internal= * Tekton Concepts =Overview= <font color=darkkhaki> * Understand the relationship between Resources and PipelineResources. * Understan...")
 
No edit summary
 
Line 18: Line 18:
* storage: an object, a directory, etc.
* storage: an object, a directory, etc.
* a [[CloudEvents|CloudEvent]]
* a [[CloudEvents|CloudEvent]]
==<span id='Input'></span>Input Resource==
=<span id='Input'></span>Input Resource=
The input is defined relative to a [[Tekton_Step#Overview|step]]. Examples of input resources are: git repository.
The input is defined relative to a [[Tekton_Step#Overview|step]]. Examples of input resources are: git repository.
==<span id='Output'></span>Output Resource==
==<span id='Output'></span>Output Resource==
The output is defined relative to a [[Tekton_Step#Overview|step]]. Examples of output resources: container image.
The output is defined relative to a [[Tekton_Step#Overview|step]]. Examples of output resources: container image.
==<tt>PipelineResource</tt>==
=<tt>PipelineResource</tt>=
Deprecated. Defines locations for [[#Input|inputs]] ingested and [[#Output|outputs]] produced by the [[Tekton_Step#Overview|steps]] in [[Tekton_Task#Overview|tasks]]. Also see [[Tekton_Task#Resources|Task Resources]].
Deprecated. Defines locations for [[#Input|inputs]] ingested and [[#Output|outputs]] produced by the [[Tekton_Step#Overview|steps]] in [[Tekton_Task#Overview|tasks]]. Also see [[Tekton_Task#Resources|Task Resources]].



Latest revision as of 04:49, 29 April 2022

Internal

Overview

Resources are used to share data between steps and tasks, and depending on which direction they are looked at, the can be input or output resources. Resources are connected to tasks and pipelines by taskRuns and pipelineRuns, respectively. A run must include the actual addresses of resources, such as the URLs of repositories, its task or pipeline needs.

Example of resources:

  • git repository
  • a pull request
  • a container image
  • a Kubernetes cluster
  • storage: an object, a directory, etc.
  • a CloudEvent

Input Resource

The input is defined relative to a step. Examples of input resources are: git repository.

Output Resource

The output is defined relative to a step. Examples of output resources: container image.

PipelineResource

Deprecated. Defines locations for inputs ingested and outputs produced by the steps in tasks. Also see Task Resources.

TO PROCESS: