diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 6a0ca8d2d..39ee103e5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -270,10 +270,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 6a45c86d3..e015441f4 100644
--- a/README.md
+++ b/README.md
@@ -242,4 +242,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