Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,17 @@ include::_attributes/common-attributes.adoc[]

toc::[]

As a cluster administrator, installing the {pipelines-title} Operator creates variants of each default cluster task known as _versioned cluster tasks_ (VCT) and _non-versioned cluster tasks_ (NVCT). For example, installing the {pipelines-title} Operator v1.7 creates a `buildah-1-7-0` VCT and a `buildah` NVCT.
As a cluster administrator, installing the {pipelines-title} Operator creates variants of each default cluster task known as _versioned cluster tasks_ (VCT) and _non-versioned cluster tasks_ (NVCT). For example, installing the {pipelines-title} Operator v1.7 creates a `buildah-1-7-0` VCT and a `buildah` NVCT.

Both NVCT and VCT have the same metadata, behavior, and specifications, including `params`, `workspaces`, and `steps`. However, they behave differently when you disable them or upgrade the Operator.
Both NVCT and VCT have the same metadata, behavior, and specifications, including `params`, `workspaces`, and `steps`. However, they behave differently when you disable them or upgrade the Operator.

[IMPORTANT]
====
In {pipelines-title} 1.10, cluster task functionality is deprecated and is planned to be removed in a future release.
====

include::modules/op-differences-between-non-versioned-and-versioned-cluster-tasks.adoc[leveloffset=+1]

include::modules/op-advantages-and-disadvantages-of-non-versioned-and-versioned-cluster-tasks.adoc[leveloffset=+1]

include::modules/op-disabling-non-versioned-and-versioned-cluster-tasks.adoc[leveloffset=+1]

6 changes: 6 additions & 0 deletions modules/op-constructing-pipelines-using-pipeline-builder.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,12 @@ In the *Developer* perspective of the console, you can use the *+Add* -> *Pipeli

* Configure pipelines using either the *Pipeline builder* or the *YAML view*.
* Construct a pipeline flow using existing tasks and cluster tasks. When you install the OpenShift Pipelines Operator, it adds reusable pipeline cluster tasks to your cluster.

[IMPORTANT]
====
In {pipelines-title} 1.10, cluster task functionality is deprecated and is planned to be removed in a future release.
====

* Specify the type of resources required for the pipeline run, and if required, add additional parameters to the pipeline.
* Reference these pipeline resources in each of the tasks in the pipeline as input and output resources.
* If required, reference any additional parameters added to the pipeline in the task. The parameters for a task are prepopulated based on the specifications of the task.
Expand Down
5 changes: 5 additions & 0 deletions modules/op-creating-pipeline-tasks.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -55,3 +55,8 @@ git-clone 1 day ago
s2i-python 1 day ago
tkn 1 day ago
----

[IMPORTANT]
====
In {pipelines-title} 1.10, cluster task functionality is deprecated and is planned to be removed in a future release.
====
5 changes: 5 additions & 0 deletions modules/op-tkn-clustertask-management.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@
[id="op-tkn-clustertask-management-commands_{context}"]
= ClusterTask management commands

[IMPORTANT]
====
In {pipelines-title} 1.10, ClusterTask functionality of the `tkn` command line utility is deprecated and is planned to be removed in a future release.
====

== clustertask
Manage ClusterTasks.

Expand Down