diff --git a/.tekton/release.yaml b/.tekton/release.yaml
index cd9ecd694..31a109a38 100644
--- a/.tekton/release.yaml
+++ b/.tekton/release.yaml
@@ -104,7 +104,7 @@ spec:
         - name: message
           value: |-
             Tekton pipelineRun $(context.pipelineRun.name) failed.
-            See https://console-openshift-console.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/k8s/ns/tekton-ci/tekton.dev~v1beta1~PipelineRun/$(context.pipelineRun.name)
+            See https://console-openshift-console.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/k8s/ns/konflux-ci/tekton.dev~v1~PipelineRun/$(context.pipelineRun.name)
             (Quick! It may disappear soon!)
         - name: key-name
           value: $(params.slack-webhook-notification-team)
diff --git a/.tekton/tag-latest.yaml b/.tekton/tag-latest.yaml
index 288b78c17..307247960 100644
--- a/.tekton/tag-latest.yaml
+++ b/.tekton/tag-latest.yaml
@@ -66,7 +66,7 @@ spec:
         - name: message
           value: |-
             Tekton pipelineRun $(context.pipelineRun.name) failed.
-            See https://console-openshift-console.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/k8s/ns/tekton-ci/tekton.dev~v1beta1~PipelineRun/$(context.pipelineRun.name)
+            See https://console-openshift-console.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/k8s/ns/konflux-ci/tekton.dev~v1~PipelineRun/$(context.pipelineRun.name)
             (Quick! It may disappear soon!)
         - name: key-name
           value: $(params.slack-webhook-notification-team)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1e64e380a..44771400c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -272,10 +272,6 @@ tag follows the expected format: `$major.$minor.$patch`, without a `v` prefix).
 should have built the image for that commit already. This is the "corresponding image" that receives
 the new version tag. If the image for the tagged commit does not exist, the release pipeline will fail.*
 
-You can watch the release pipeline in the [OpenShift console][ocp-cachi2-pipelines] in case it fails
-(the pipeline is not visible anywhere in GitHub UI). For intermittent failures, retrying should be
-possible from the OpenShift UI or by deleting and re-pushing the version tag.
-
 *⚠ The release pipeline runs as soon as you push a tag into the repository. Do not push the new version
 tag until you are ready to publish the release. You can use GitHub's ability to auto-create the tag
 upon publishment.*
diff --git a/README.md b/README.md
index b7a82f99f..a650e9e30 100644
--- a/README.md
+++ b/README.md
@@ -272,4 +272,3 @@ still in early development phase.
 [go118-changelog]: https://tip.golang.org/doc/go1.18#go-command
 [go119-changelog]: https://tip.golang.org/doc/go1.19#go-command
 [go121-changelog]: https://tip.golang.org/doc/go1.21
-[ocp-cachi2-pipelines]: https://console-openshift-console.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/pipelines/ns/tekton-ci/pipeline-runs?name=cachi2