Improve Backing up your internal image registry to IBM Cloud Object Storage #191
Description
Which topic are you reporting about?
The page https://cloud.ibm.com/docs/openshift?topic=openshift-registry&q=10.21&tags=openshift#cos_image_registry currently states the following:
However, if the bucket fails to create when you create your cluster, you must manually create a bucket and set up your cluster to use the bucket. In the meantime, the internal registry uses an emptyDir Kubernetes volume that stores your container images on the secondary disk of your worker node. The emptyDir volumes are not considered persistent highly available storage, and if you delete the pods that use the image, the image is automatically deleted.
To manually create a bucket for your internal registry, see [Cluster create error about cloud object storage bucket](https://cloud.ibm.com/docs/openshift?topic=openshift-ts_cos_bucket_cluster_create).
What do you think needs to be updated?
I would add a section in this page that contains this readme content
https://github.com/lionelmace/ibmcloud-utils/blob/master/openshift/registry/configure-cos-registry.md
Anything else?
No response