RHDEVDOCS-6210: Remove deprecated ClusterTask from docs

_topic_maps/_topic_map.yml

@@ -74,8 +74,6 @@ Topics:
   File: using-manual-approval
 - Name: Using Red Hat entitlements in pipelines
   File: using-rh-entitlements-pipelines
-- Name: Managing non-versioned and versioned cluster tasks
-  File: managing-nonversioned-and-versioned-cluster-tasks
 ---
 Name: Observability in OpenShift Pipelines
 Dir: records

create/creating-applications-with-cicd-pipelines.adoc

@@ -37,12 +37,6 @@ include::modules/op-creating-project-and-checking-pipeline-service-account.adoc[
 
 include::modules/op-creating-pipeline-tasks.adoc[leveloffset=+1]
 
-[role="_additional-resources"]
-[id="additional-resources-creating_{context}"]
-.Additional resources
-
-* xref:../create/managing-nonversioned-and-versioned-cluster-tasks.adoc#managing-nonversioned-and-versioned-cluster-tasks[Managing non-versioned and versioned cluster tasks]
-
 include::modules/op-assembling-a-pipeline.adoc[leveloffset=+1]
 
 include::modules/op-mirroring-images-to-run-pipelines-in-restricted-environment.adoc[leveloffset=+1]

create/remote-pipelines-tasks-resolvers.adoc

@@ -85,6 +85,7 @@ include::modules/op-resolver-cluster-tasks-ref.adoc[leveloffset=+1]
 
 include::modules/op-resolver-stepactions-ref.adoc[leveloffset=+1]
 
+include::modules/op-resolver-tasks-step-actions-about.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 [id="additional-resources_{context}"]

install_config/customizing-configurations-in-the-tektonconfig-cr.adoc

@@ -13,7 +13,7 @@ In {pipelines-title}, you can customize the following configurations by using th
 * Changing the default service account
 * Disabling the service monitor
 * Configuring pipeline resolvers
-* Disabling cluster tasks and pipeline templates
+* Disabling pipeline templates
 * Disabling the integration of {tekton-hub}
 * Disabling the automatic creation of RBAC resources
 * Pruning of task runs and pipeline runs
@@ -41,7 +41,7 @@ include::modules/op-disabling-the-service-monitor.adoc[leveloffset=+1]
 
 include::modules/op-configuring-pipeline-resolvers.adoc[leveloffset=+1]
 
-include::modules/op-disabling-cluster-tasks-and-pipeline-templates.adoc[leveloffset=+1]
+include::modules/op-disabling-pipeline-templates.adoc[leveloffset=+1]
 
 include::modules/op-disabling-the-integretion-of-tekton-hub.adoc[leveloffset=+1]
 
@@ -63,6 +63,5 @@ include::modules/op-additional-options-webhooks.adoc[leveloffset=+1]
 == Additional resources
 
 * xref:../secure/authenticating-pipelines-repos-using-secrets.adoc#authenticating-pipelines-repos-using-secrets[Authenticating pipelines with repositories using secrets]
-* xref:../create/managing-nonversioned-and-versioned-cluster-tasks.adoc#managing-nonversioned-and-versioned-cluster-tasks[Managing non-versioned and versioned cluster tasks]
 * xref:../create/working-with-pipelines-web-console.adoc#using-custom-pipeline-template-for-git-import_working-with-pipelines-web-console[Creating pipeline templates in the Administrator perspective]
 * link:https://docs.openshift.com/container-platform/latest/applications/pruning-objects.html[Pruning objects to reclaim resources]

modules/op-about-pipelines-as-code-resolver.adoc

@@ -13,7 +13,6 @@ If {pac} cannot resolve the referenced tasks in the `Pipeline` or `PipelineSpec`
 
 The resolver skips resolving if it observes the following type of tasks:
 
-* A reference to a cluster task.
 * A task or pipeline bundle.
 * A custom task with an API version that does not have a `tekton.dev/` prefix.
 

modules/op-constructing-pipelines-using-pipeline-builder.adoc

@@ -9,13 +9,7 @@
 In the *Developer* perspective of the console, you can use the *+Add* -> *Pipeline* -> *Pipeline builder* option to:
 
 * 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 {pipelines-shortname} Operator, it adds reusable pipeline cluster tasks to your cluster.
-
-[IMPORTANT]
-====
-In {pipelines-title} 1.10, `ClusterTask` functionality is deprecated and is planned to be removed in a future release.
-====
-
+* Construct a pipeline flow using existing tasks. When you install the {pipelines-shortname} Operator, it adds reusable pipeline tasks to your cluster that can be used with the cluster resolver.
 * 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.
@@ -25,7 +19,7 @@ In {pipelines-title} 1.10, `ClusterTask` functionality is deprecated and is plan
 [IMPORTANT]
 ====
 In the developer perspective, you can create a customized pipeline using your own set of curated tasks. To search, install, and upgrade your tasks directly from the developer console, your cluster administrator needs to install and deploy a local Tekton Hub instance and link that hub to the OpenShift Container Platform cluster. For more details, see _Using Tekton Hub with {pipelines-shortname}_ in the _Additional resources_ section.
-If you do not deploy any local Tekton Hub instance, by default, you can only access the cluster tasks, namespace tasks and public Tekton Hub tasks.
+If you do not deploy any local Tekton Hub instance, by default, you can only access namespace tasks and public Tekton Hub tasks.
 ====
 
 .Procedure

modules/op-creating-pipeline-tasks.adoc

@@ -31,31 +31,3 @@ NAME                DESCRIPTION   AGE
 apply-manifests                   1 minute ago
 update-deployment                 48 seconds ago
 ----
-
-. Use the `tkn clustertasks list` command to list the Operator-installed additional cluster tasks such as `buildah` and `s2i-python`:
-+
-[NOTE]
-====
-To use the `buildah` cluster task in a restricted environment, you must ensure that the Dockerfile uses an internal image stream as the base image.
-====
-+
-[source,terminal]
-----
-$ tkn clustertasks list
-----
-+
-The output lists the Operator-installed `ClusterTask` resources:
-+
-[source,terminal]
-----
-NAME                       DESCRIPTION   AGE
-buildah                                  1 day ago
-git-clone                                1 day ago
-s2i-python                               1 day ago
-tkn                                      1 day ago
-----
-
-[IMPORTANT]
-====
-In {pipelines-title} 1.10, `ClusterTask` functionality is deprecated and is planned to be removed in a future release.
-====

modules/op-disabling-automatic-creation-of-rbac-resources.adoc

@@ -9,6 +9,17 @@ The default installation of the {pipelines-title} Operator creates multiple role
 
 To disable the automatic creation of cluster-wide RBAC resources after the {pipelines-title} Operator is installed, cluster administrators can set the `createRbacResource` parameter to `false` in the cluster-level `TektonConfig` custom resource (CR).
 
+.Procedure
+
+. Edit the `TektonConfig` CR by running the following command:
++
+[source,terminal]
+----
+$ oc edit TektonConfig config
+----
+
+. In the `TektonConfig` CR, set the `createRbacResource` param value to `false`:
+
 .Example `TektonConfig` CR
 [source,yaml]
 ----
@@ -20,11 +31,5 @@ spec:
   params:
   - name: createRbacResource
     value: "false"
-...
+# ...
 ----
-
-[WARNING]
-====
-As a cluster administrator or an user with appropriate privileges, when you disable the automatic creation of RBAC resources for all namespaces, the default `ClusterTask` resource does not work. For the `ClusterTask` resource to function, you must create the RBAC resources manually for each intended namespace.
-====
-

modules/op-disabling-pipeline-templates.adoc

@@ -0,0 +1,44 @@
+// This module is included in the following assemblies:
+// * install_config/customizing-configurations-in-the-tektonconfig-cr.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="op-disabling-pipeline-templates_{context}"]
+= Disabling resolver tasks and pipeline templates
+
+By default, the `TektonAddon` custom resource (CR) installs `resolverTasks` and `pipelineTemplates` resources along with {pipelines-shortname} on the cluster.
+
+You can disable the installation of the resolver tasks and pipeline templates by setting the parameter value to `false` in the `.spec.addon` specification.
+
+.Procedure
+
+. Edit the `TektonConfig` CR by running the following command:
++
+[source,terminal]
+----
+$ oc edit TektonConfig config
+----
+
+. In the `TektonConfig` CR, set the `resolverTasks` and `pipelineTemplates` parameter value in `.addon.params` spec to `false`:
++
+.Example of disabling resolver task and pipeline template resources
+[source,yaml]
+----
+apiVersion: operator.tekton.dev/v1alpha1
+kind: TektonConfig
+metadata:
+  name: config
+spec:
+# ...
+  addon:
+    params:
+      - name: resolverTasks
+        value: 'false'
+      - name: pipelineTemplates
+        value: 'false'
+# ...
+----
++
+[IMPORTANT]
+====
+You can set the value of the `pipelinesTemplates` parameter to `true` only when the value of the `resolverTasks` parameter is `true`.
+====

modules/op-installing-pipelines-operator-in-web-console.adoc

@@ -22,7 +22,7 @@ The supported profiles are:
 
 * Lite: This installs only Tekton Pipelines.
 * Basic: This installs Tekton Pipelines, Tekton Triggers, and Tekton Chains.
-* All: This is the default profile used when the `TektonConfig` CR is installed. This profile installs all of the Tekton components, including Tekton Pipelines, Tekton Triggers, Tekton Chains, {pac}, and Tekton Addons. Tekton Addons includes the `ClusterTasks`, `ClusterTriggerBindings`, `ConsoleCLIDownload`, `ConsoleQuickStart`, and `ConsoleYAMLSample` resources, as well as the tasks available using the cluster resolver from the `openshift-pipelines` namespace.
+* All: This is the default profile used when the `TektonConfig` CR is installed. This profile installs all of the Tekton components, including Tekton Pipelines, Tekton Triggers, Tekton Chains, {pac}, and Tekton Addons. Tekton Addons includes the `ClusterTriggerBindings`, `ConsoleCLIDownload`, `ConsoleQuickStart`, and `ConsoleYAMLSample` resources, as well as the tasks and step actions available using the cluster resolver from the `openshift-pipelines` namespace.
 
 [discrete]
 .Procedure

modules/op-nonroot-buildah-user-namespaces.adoc

@@ -42,7 +42,7 @@ metadata:
   name: assemble-containerimage
   namespace: pipeline-namespace
 spec:
-  description: This cluster task builds an image.
+  description: This task builds an image.
 #  ...
   stepTemplate:
     env: