Disabling Tekton Hub login after upgrading from OpenShift Pipelines 1.7.x --> 1.8.x
Updated
- In OpenShift Pipelines 1.7.x, to install Tekton Hub, the user had to create an API
Secretnamedtekton-hub-apiand then apply the Hub custom resource (CR). - But the OpenShift Pipelines 1.8.x release adds a feature where the user does not need to create the API secret. They need to apply the CR, and Hub will be up and running. In that case, login and rating will be disabled by default
NOTE: Disable Tekton Hub Auth and Rating works only on a fresh instance of Hub but doesn't work when the user upgrades from 1.7.x --> 1.8.x
To achieve disabling auth when a user upgrades from 1.7.x --> 1.8.x, perform the following steps.
Step 1: Delete the Tekton Hub API secret which you have created:
oc delete secret tekton-hub-api -n <targetNamespace>
Step 2: Delete the Installerset for Tekton Hub API
oc delete tektoninstallerset tekton-hub-api-mv5dv
NOTE:- It will automatically recreate the Tekton Hub API installerset.
- Wait until the Tekton Hub status becomes true again
╰─ oc get tektonhub hub
NAME VERSION READY REASON APIURL UIURL
hub 1.8.0 True https://tekton-hub-api-openshift-pipelines.apps.ci-ln-279pdpk-72292.origin-ci-int-gce.dev.rhcloud.com https://tekton-hub-ui-openshift-pipelines.apps.ci-ln-279pdpk-72292.origin-ci-int-gce.dev.rhcloud.com
Step 3: Delete the UI config map
oc delete configmap tekton-hub-ui -n <targetNamespace>
Step 4: Delete the Installerset for Tekton Hub UI
oc delete tektoninstallerset tekton-hub-ui-c8v7s
NOTE:- It will automatically recreate the Tekton Hub UI installerset.
- Wait until the Tekton Hub status becomes true again
╰─ oc get tektonhub hub
NAME VERSION READY REASON APIURL UIURL
hub 1.8.0 True https://tekton-hub-api-openshift-pipelines.apps.ci-ln-279pdpk-72292.origin-ci-int-gce.dev.rhcloud.com https://tekton-hub-ui-openshift-pipelines.apps.ci-ln-279pdpk-72292.origin-ci-int-gce.dev.rhcloud.com
Product(s)
Category
Tags
Article Type