A customer might have many OCP clusters. To help them know which cluster the oc is connecting to extract the CRs, it'll be great to include cluster identity in the output of the cli.

./oc adm release extract --to 4.14.update --included --credentials-requests registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-08-11-055332 -a docker.config
Extracted release payload from digest sha256:8a5507bf897252cab6d1957d9477bce45e7427f4f798450605d3503aed936594 created at 2023-08-11T05:55:14Z

Always

1. Install a cluster
2. Extract CRs by connecting the cluster 
$ ./oc adm release extract --to 4.14.update --included --credentials-requests registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-08-11-055332 -a docker.config
Extracted release payload from digest sha256:8a5507bf897252cab6d1957d9477bce45e7427f4f798450605d3503aed936594 created at 2023-08-11T05:55:14Z

 3.

oc returns the message where we can't know which cluster it was connecting to

Extracted release payload from digest sha256:8a5507bf897252cab6d1957d9477bce45e7427f4f798450605d3503aed936594 created at 2023-08-11T05:55:14Z

The message that oc returns includes the cluster identity