Document URL ============ https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/managing_hybrid_and_multicloud_resources/accessing-the-rados-object-gateway-s3-endpoint_rhocs Section Number and Name ======================= Chapter 12. Accessing the RADOS Object Gateway S3 endpoint Describe the issue ================== The procedure in the chapter suggests to manually expose RGW service to create RGW public route (so that RGW endpoint will be available outside of the cluster). But looking at behaviour in OCS 4.8 cluster (and if I recall right, I have seen this in OCS 4.7 as well), this is no longer necessary, as the public route already exists: ``` $ oc get route -n openshift-storage NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD noobaa-mgmt noobaa-mgmt-openshift-storage.apps.mbukatov-0513b.qe.rh-ocs.com noobaa-mgmt mgmt-https reencrypt/Redirect None ocs-storagecluster-cephobjectstore ocs-storagecluster-cephobjectstore-openshift-storage.apps.mbukatov-0513b.qe.rh-ocs.com rook-ceph-rgw-ocs-storagecluster-cephobjectstore <all> None s3 s3-openshift-storage.apps.mbukatov-0513b.qe.rh-ocs.com s3 s3-https reencrypt None ``` Suggestions for improvement =========================== Drop the steps about exposing RGW service, and mention the name of the default RWG route instead. Additional information ====================== Reach out to noobaa team to confirm since when OCS release the RGW route is created by default.
IIUC, for verification, the removal of RGW service exposure procedure has to be validated across 4.7, 4.8, 4.9, 4.10 Erin, please confirm
There is a step `Replace <ENDPOINT> with the route that you get from the command in step 3. ` in Verification section but I don't see any step 3 where I can find the endpoint. There is only step 1 `Run oc get service command to get the RGW service name.`in Procedure section.