Description of problem: It looks like the sample yaml file is for S3, not for OCS. Version-Release number of selected component (if applicable): ACM 2.2 OCP 4.7 How reproducible: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.2/html-single/observing_environments/index#enabling-observability Steps to Reproduce: 1. "OBSERVING ENVIRONMENTS" https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.2/html-single/observing_environments/index#enabling-observability 2."1.2.1. Enabling observability" 3."Create a secret for your object storage. Your secret must contain the credentials to your storage solution. For example, run the following command:" 4. "i. View the following examples of secrets for the supported object stores:" 5. "iv. For OpenShift Container Storage, your secret might resemble the following file:" Actual results: type: s3 config: bucket: YOUR_S3_BUCKET endpoint: YOUR_OCS_ENDPOINT insecure: true access_key: YOUR_OCS_ACCESS_KEY secret_key: YOUR_OCS_SECRET_KEY Expected results: I would expect to see the information/settings for OCS instead of S3. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Advanced Cluster Management 2.2.4 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2461