update references to forum-testplatform to forum-ocp-testplatform (openshift#41483)

* update references to forum-testplatform to forum-ocp-testplatform

* update references to coreos.slack.com to redhat-internal.slack.com

---------

Co-authored-by: smg247 <[email protected]>

Author: smg247

ci-operator/SECRETS.md

@@ -6,7 +6,7 @@ they should be deployed to the cluster.
 There are currently two ways to manager secrets:
 
 * DPTP-managed Secrets: We store secrets in a private secret storage system: [Bitwarden](https://bitwarden.com/).
-To add new secrets to this storage please reach out to `#forum-testplatform` on Slack
+To add new secrets to this storage please reach out to `#forum-ocp-testplatform` on Slack
 and be prepared to encrypt your data with our GPG keys. DPTP uses [ci-secret-bootstrap](../core-services/ci-secret-bootstrap)
 to populate secrets from Bitwarden to the clusters in CI-infrastructure.
 

clusters/app.ci/openshift-user-workload-monitoring/README.md

@@ -20,5 +20,5 @@ The metrics and the alerts defined here are for the TP team. CI users has [a mor
 
 ## Dashboards
 
-Currently there is [no dashboard support in UWM](https://coreos.slack.com/archives/C0VMT03S5/p1670228152637209?thread_ts=1670008515.321099&cid=C0VMT03S5).
+Currently there is [no dashboard support in UWM](https://redhat-internal.slack.com/archives/C0VMT03S5/p1670228152637209?thread_ts=1670008515.321099&cid=C0VMT03S5).
 Dashboards for ci-monitoring based on those metrics are deployed in [ci-grafana](../ci-grafana).

clusters/build-clusters/01_cluster/assets/admin_default_clusterautoscaler.yaml

@@ -1,5 +1,5 @@
 #https://docs.openshift.com/container-platform/4.2/machine_management/applying-autoscaling.html
-#https://coreos.slack.com/archives/CBZHF4DHC/p1578326297014800
+#https://redhat-internal.slack.com/archives/CBZHF4DHC/p1578326297014800
 #oc --kubeconfig ./.kube/build01.config get machine -n openshift-machine-api
 #NAME                                    STATE     TYPE         REGION      ZONE         AGE
 #build01-88trw-master-0                  running   m5.2xlarge   us-east-1   us-east-1a   81d

clusters/build-clusters/02_cluster/README.md

@@ -89,7 +89,7 @@ The default one would be `default-route-openshift-image-registry.apps.build02.gc
 
 [Steps](https://docs.openshift.com/container-platform/4.4/registry/securing-exposing-registry.html):
 
-* [dns set up](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes): [No official doc yet](https://coreos.slack.com/archives/CCH60A77E/p1588774688400500).
+* [dns set up](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes): [No official doc yet](https://redhat-internal.slack.com/archives/CCH60A77E/p1588774688400500).
 
 ```
 oc --context build02 get svc -n openshift-ingress router-default 

clusters/build-clusters/02_cluster/openshift-machine-api/admin_default_clusterautoscaler.yaml

@@ -1,5 +1,5 @@
 #https://docs.openshift.com/container-platform/4.2/machine_management/applying-autoscaling.html
-#https://coreos.slack.com/archives/CBZHF4DHC/p1578326297014800
+#https://redhat-internal.slack.com/archives/CBZHF4DHC/p1578326297014800
 #oc --context build02 get machine -n openshift-machine-api
 #NAME                     PHASE     TYPE             REGION     ZONE         AGE
 #build0-gstfj-m-0         Running   n1-standard-8    us-east1   us-east1-b   3d22h

clusters/build-clusters/arm01/assets/admin_default_clusterautoscaler.yaml

@@ -1,5 +1,5 @@
 #https://docs.openshift.com/container-platform/4.11/machine_management/applying-autoscaling.html
-#https://coreos.slack.com/archives/CBZHF4DHC/p1578326297014800
+#https://redhat-internal.slack.com/archives/CBZHF4DHC/p1578326297014800
 #oc --kubeconfig ./.kube/arm01.config get machine -n openshift-machine-api
 #NAME                                        PHASE     TYPE           REGION      ZONE         AGE
 #arm-build01-dh7m2-master-3                  Running   m6gd.2xlarge   us-east-1   us-east-1c   38d

docs/dptp-triage-sop/infrastructure-jobs.md

@@ -208,7 +208,7 @@ The repo is in a bad state where someone has pushed directly to the future relea
 #### Resolution
 
 1. Identify the owner(s) of the repo
-2. Reach out and tag them in `#forum-testplatform` asking them to clean up the affected branch.
+2. Reach out and tag them in `#forum-ocp-testplatform` asking them to clean up the affected branch.
 3. This job runs hourly, so silencing the alert until they can clean it up is a good idea. 
 
 

projects/azure/README.md

@@ -117,7 +117,7 @@ If you don't find a match, you should open a new issue to track the new failure
 Otherwise, link the existing issue in your PR. Then, you can `/retest` your PR.
 
 For any infrastructure-related issues, make sure to contact the Developer Productivity
-team who is responsible for managing the OpenShift CI Infrastructure at [#forum-testplatform](https://coreos.slack.com/).
+team who is responsible for managing the OpenShift CI Infrastructure at [#forum-ocp-testplatform](https://redhat-internal.slack.com/).
 
 Optionally, you can request specific long-running tests to run that are not
 running in PRs by default.
@@ -282,7 +282,7 @@ ask an existing member of the `azure-team` group to apply the changes on the clu
 oc apply -f cluster-wide.yaml
 ``
 
-In general, all changes in `projects/azure/` are not automatically applied in the CI cluster. CI admins can be contacted at [#forum-testplatform](https://coreos.slack.com/). After your
+In general, all changes in `projects/azure/` are not automatically applied in the CI cluster. CI admins can be contacted at [#forum-ocp-testplatform](https://redhat-internal.slack.com/). After your
 pull request is merged, apart from updating the group, you should be able to `oc apply` all other changes
 in the `azure` namespace.