Current documented instructions for gathering data on Hub clusters (default oc adm must-gather) are insufficient for accurate RDS verification.Testing revealed that using the standard collection method results in a 35+ false positive rate for reported "missing files" . These objects actually exist but are not collected in the necessary granularity for the tool to detect them.

1.Log in to a target Telco OCP Hub Cluster (e.g., OCP 4.18 / 4.19).     
2.Follow the current RDS verification instructions and run the default: oc adm must-gather.
3.Run the cluster-compare tool against this data using the RDS metadata.yaml reference. Observe the "Missing Files" section in the RDS compliance report.
     

The RDS compliance report flags 34+ missing files across critical categories (Storage, Registry, ACM, GitOps, Logging).
Manual verification confirms these are 100% false positives; the resources are present on the cluster but were missed by the standard collection scope.

The resulting cluster-compare report should accurately reflect the cluster's state, showing only the real deviations and/or missing files for a compliant cluster, ensuring trust in the RDS Dashboard.    

Commands to include as part of the correct must-gather step prior to RDS analysis for OCP Hub 4.18+:

# 1. Must-gather
oc adm must-gather --all-images

# 2. Cluster-scoped resources
oc adm inspect clusterroles,clusterrolebindings,namespaces,nodes --dest-dir=./cluster-scoped

# 3. Registry and operators
oc adm inspect imagedigestmirrorset,imagetagmirrorset,catalogsource,clusterserviceversion,customresourcedefinition,operatorhub --dest-dir=./cluster-config