RHDEVDOCS-7542: Removing all instances of Tekton hub from Pipelines docs

_topic_maps/_topic_map.yml

@@ -126,13 +126,6 @@ Topics:
 - Name: Using buildah-ns tekton task
   File: using-buildah-ns-tekton-task
 ---
-Name: Custom Tekton Hub instance
-Dir: hub
-Distros: openshift-pipelines
-Topics:
-- Name: Using Tekton Hub with OpenShift Pipelines
-  File: using-tekton-hub-with-openshift-pipelines
----
 Name: Pipelines CLI (tkn) reference
 Dir: tkn_cli
 Distros: openshift-pipelines

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

@@ -85,6 +85,5 @@ include::modules/op-validating-pull-requests-using-GitHub-interceptors.adoc[leve
 * For more details on pipelines in the *Developer* perspective, see the xref:../create/working-with-pipelines-web-console.adoc#working-with-pipelines-web-console[Working with {pipelines-shortname} in the web console] section.
 * To learn more about Security Context Constraints (SCCs), see the link:https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html[Managing Security Context Constraints] section.
 * For more examples of reusable tasks, see the link:https://github.com/openshift/pipelines-catalog[OpenShift Catalog] repository. Additionally, you can also see the Tekton Catalog in the Tekton project.
-* To install and deploy a custom instance of {tekton-hub} for reusable tasks and pipelines, see xref:../hub/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using {tekton-hub} with {pipelines-title}].
 * For more details on re-encrypt TLS termination, see link:https://docs.openshift.com/container-platform/3.11/architecture/networking/routes.html#re-encryption-termination[Re-encryption Termination].
 * For more details on secured routes, see the link:https://docs.openshift.com/container-platform/latest/networking/routes/secured-routes.html[Secured routes] section.

create/remote-pipelines-tasks-resolvers.adoc

@@ -17,7 +17,7 @@ In these cases, the _resolvers_ in {pipelines-title} retrieve the pipeline, task
 
 The following resolvers are available in a default installation of {pipelines-title}:
 
-Hub resolver:: Retrieves a task, pipeline, or `StepAction` definition from the Pipelines Catalog available on {artifact-hub} or {tekton-hub}.
+Hub resolver:: Retrieves a task, pipeline, or `StepAction` definition from the Pipelines Catalog available on {artifact-hub}.
 Bundles resolver:: Retrieves a task, pipeline, or `StepAction` definition from a Tekton bundle, which is an OCI image available from any OCI repository, such as an OpenShift container repository.
 Git resolver:: Retrieves a task, pipeline, or `StepAction` definition from a Git repository. You must specify the repository, the branch, and the path.
 HTTP resolver:: Retrieves a task, pipeline, or `StepAction` definition from a remote HTTP or HTTPS URL. You must specify the URL for authentication.
@@ -61,8 +61,3 @@ include::modules/op-resolver-community-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"]
-== Additional resources
-
-* xref:../hub/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using {tekton-hub} with {pipelines-shortname}]

create/working-with-pipelines-web-console.adoc

@@ -32,11 +32,6 @@ include::modules/op-editing-pipelines.adoc[leveloffset=+2]
 
 include::modules/op-deleting-pipelines.adoc[leveloffset=+2]
 
-[role="_additional-resources"]
-.Additional resources
-
-* xref:../hub/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using {tekton-hub} with {pipelines-shortname}]
-
 // Admin console
 include::modules/op-creating-pipeline-templates-admin-console.adoc[leveloffset=+1]
 

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

@@ -15,7 +15,6 @@ In {pipelines-title}, you can customize the following configurations by using th
 * Disabling the service monitor
 * Configuring pipeline resolvers
 * Disabling pipeline templates
-* Disabling the integration of {tekton-hub}
 * Disabling the automatic creation of RBAC resources
 * Pruning of task runs and pipeline runs
 
@@ -41,8 +40,6 @@ include::modules/op-disabling-pipeline-templates.adoc[leveloffset=+1]
 
 include::modules/op-disabling-pipeline-triggers.adoc[leveloffset=+1]
 
-include::modules/op-disabling-the-integretion-of-tekton-hub.adoc[leveloffset=+1]
-
 include::modules/op-migrating-from-tekton-hub-to-artifact-hub.adoc[leveloffset=+1]
 
 include::modules/op-assess-migration-impact.adoc[leveloffset=+2]

install_config/installing-pipelines.adoc

@@ -35,8 +35,6 @@ include::modules/op-pipelines-operator-in-restricted-environment.adoc[leveloffse
 
 * xref:../records/using-tekton-results-for-openshift-pipelines-observability.adoc#using-tekton-results-for-openshift-pipelines-observability[Using {tekton-results} for {pipelines-shortname} observability]
 
-* xref:../hub/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using {tekton-hub} with {pipelines-title}]
-
 * xref:../create/creating-applications-with-cicd-pipelines.adoc#op-mirroring-images-to-run-pipelines-in-restricted-environment_creating-applications-with-cicd-pipelines[Mirroring images to run pipelines in a restricted environment]
 
 * link:https://docs.openshift.com/container-platform/latest/openshift_images/configuring-samples-operator.html#samples-operator-restricted-network-install[Configuring Samples Operator for a restricted cluster]

modules/op-additional-options-webhooks.adoc

@@ -127,25 +127,4 @@ spec:
           failurePolicy: Fail
           timeoutSeconds: 20
           sideEffects: None
-----
-+
-.Example settings for the {tekton-hub} controller
-[source,yaml]
-----
-apiVersion: operator.tekton.dev/v1
-kind: TektonConfig
-metadata:
-  name: config
-spec:
-  hub:
-    options:
-      webhookConfigurationOptions:
-        validation.webhook.hub.tekton.dev:
-          failurePolicy: Fail
-          timeoutSeconds: 20
-          sideEffects: None
-        webhook.hub.tekton.dev:
-          failurePolicy: Fail
-          timeoutSeconds: 20
-          sideEffects: None
-----
+----

modules/op-assess-migration-impact.adoc

@@ -11,7 +11,6 @@ You must migrate to {artifact-hub} to ensure uninterrupted catalog resolution.
 You must migrate if:
 
 * Your Tekton resources reference `type: tekton` or `catalog: Tekton`.
-* You rely on {tekton-hub} as a hosted catalog service.
 
 Use the following scripts to identify which Tekton resources require modification and to verify the hub resolver configuration on your cluster.
 

modules/op-configuring-pipeline-resolvers.adoc

@@ -11,7 +11,6 @@ You can enable or disable specific pipeline resolvers, such as git, cluster, bun
 * `enable-bundles-resolver`
 * `enable-cluster-resolver`
 * `enable-git-resolver`
-* `enable-hub-resolver`
 
 .Example
 [source,yaml]
@@ -25,7 +24,6 @@ spec:
     enable-bundles-resolver: true
     enable-cluster-resolver: true
     enable-git-resolver: true
-    enable-hub-resolver: true
 ----
 
 You can also give resolver specific configurations in the `TektonConfig` CR. For example, define the following fields in the `map[string]string` format to set configurations for each pipeline resolver:
@@ -45,6 +43,4 @@ spec:
       default-namespace: test
     git-resolver-config:
       server-url: localhost.com
-    hub-resolver-config:
-      default-tekton-hub-catalog: tekton
 ----

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

@@ -14,13 +14,6 @@ In the *Developer* perspective of the console, you can use the *+Add* -> *Pipeli
 * 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 Pipeline Builder prepopulates the task parameters based on the task specifications.
 * Use the Operator-installed, reusable snippets and samples to create detailed pipelines.
-* Search and add tasks from your configured local {tekton-hub} instance.
-
-[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 {product-title} 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 namespace tasks and public {tekton-hub} tasks.
-====
 
 .Procedure
 
@@ -45,7 +38,7 @@ image::op-pipeline-yaml.png[YAML view of the Pipeline builder]
 +
 [NOTE]
 ====
-The search list has all the {tekton-hub} tasks and tasks available in the cluster. Also, if a task is already installed, it will show *Add* to add the task, whereas it will show *Install and add* to install and add the task. It will show *Update and add* when you add the same task with an updated version.
+The search list has all the tasks available in the cluster. Also, if a task is already installed, it will show *Add* to add the task, whereas it will show *Install and add* to install and add the task. It will show *Update and add* when you add the same task with an updated version.
 ====
 
 *** To add sequential tasks to the pipeline: