1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/op-disabling-tekton-hub-authorization-after-upgrade.adoc

89 lines
3.2 KiB
Plaintext

// This module is included in the following assembly:
//
// *cicd/pipelines/using-tekton-hub-with-openshift-pipelines.adoc
:_mod-docs-content-type: PROCEDURE
[id="disabling-tekton-hub-authorization-after-upgrade_{context}"]
= Disabling {tekton-hub} authorization after upgrading the {pipelines-title} Operator from 1.7 to 1.8
[role="_abstract"]
When you install {tekton-hub} with {pipelines-title} Operator 1.8, the login authorization and ratings for the {tekton-hub} artifacts are disabled for the default installation. However, when you upgrade the Operator from 1.7 to 1.8, the instance of the {tekton-hub} on your cluster does not automatically disable the login authorization and ratings.
To disable login authorization and ratings for {tekton-hub} after upgrading the Operator from 1.7 to 1.8, perform the steps in the following procedure.
[discrete]
.Prerequisites
* Ensure that the {pipelines-title} Operator is installed in the default `openshift-pipelines` namespace on the cluster.
[discrete]
.Procedure
. Delete the existing {tekton-hub} API secret that you created while manually installing {tekton-hub} for Operator 1.7.
+
[source,terminal]
----
$ oc delete secret tekton-hub-api -n <targetNamespace> <1>
----
<1> The common namespace for the {tekton-hub} API secret and the {tekton-hub} CR. By default, the target namespace is `openshift-pipelines`.
. Delete the `TektonInstallerSet` object for the {tekton-hub} API.
+
[source,terminal]
----
$ oc get tektoninstallerset -o name | grep tekton-hub-api | xargs oc delete
----
+
[NOTE]
====
After deletion, the Operator automatically creates a new {tekton-hub} API installer set.
====
+
Wait and check the status of the {tekton-hub}. Proceed to the next steps when the `READY` column displays `True`.
+
[source,terminal]
----
$ oc get tektonhub hub
----
+
.Sample output
[source,terminal]
----
NAME VERSION READY REASON APIURL UIURL
hub 1.8.0 True https://tekton-hub-api-openshift-pipelines.apps.example.com https://tekton-hub-ui-openshift-pipelines.apps.example.com
----
. Delete the `ConfigMap` object for the {tekton-hub} UI.
+
[source,terminal]
----
$ oc delete configmap tekton-hub-ui -n <targetNamespace> <1>
----
<1> The common namespace for the {tekton-hub} UI and the {tekton-hub} CR. By default, the target namespace is `openshift-pipelines`.
. Delete the `TektonInstallerSet` object for the {tekton-hub} UI.
+
[source,terminal]
----
$ oc get tektoninstallerset -o name | grep tekton-hub-ui | xargs oc delete
----
+
[NOTE]
====
After deletion, the Operator automatically creates a new {tekton-hub} UI installer set.
====
+
Wait and check the status of the {tekton-hub}. Proceed to the next steps when the `READY` column displays `True`.
+
[source,terminal]
----
$ oc get tektonhub hub
----
+
.Sample output
[source,terminal]
----
NAME VERSION READY REASON APIURL UIURL
hub 1.8.0 True https://tekton-hub-api-openshift-pipelines.apps.example.com https://tekton-hub-ui-openshift-pipelines.apps.example.com
----