It doesn't have read-after-write consistency guarantees, which means that even if you fix your permissions, it's possible for pushes to fail. Installing openshift origin 3.9 from the release-3.9 branch (using the test repo from here: openshift/origin#19196) fails on the registry check: openshift_hosted_registry_storage_kind;nfs is an unsupported type for openshift_hosted_registry_storage_kind. I don't have a solution for your permissions issue, but we strongly recommend against NFS for storage for the registry. So there is a workaround: 1. create an NFS PV and PVC. If you installed OpenShift Origin like here, a Registry Pod has already been deployed and running, but if you'd like to change settings of the Pod like storage, configute like follows. Specify the name of an existing pull secret to be used for pulling component images from an authenticated registry. openshift_enable_unsupported_configurations=True …
OpenShift setup configures and starts a default persistent warehouse, which is shared by NFS and is controlled by OpenShift in the Inventory file_ hosted_ registry_ storage_ *Variable definition. openshift_logging_curator_default_days. Description. You can store your Docker images with OpenShift's default registry, or with Container Registry. If not, change it: Apps can leverage any Google service that fits your use case, such as BigQuery, or AI Platform.
... For example, if your NFS storage volume is mounted at /nfs… OpenShift leverages several other Google Cloud resources for critical components. Cloud Storage provides persistent storage for your apps. From: Andy Goldstein
The 100GB drive is for NFS and will be persistent storage for the OpenShift registry. Create a persistent volume on the NFS share.
Citing the bug description: Additional info: Creating a PV/PVC out of the same NFS share appears to work fine. Therefore, I'm lowering priority. Maintain regulatory compliance and focus on your application development, while your master, infrastructure, and application nodes are patched, updated, … The default minimum age (in days) Curator uses for deleting log records. To see if you’ve specified a selector, type oc edit dc/docker-registry and search for nodeSelector.If this value is not defined, it is easier to delete the entire registry and re-create it with the - … Deploy Docker Registry.
To configure the Unity NFS volume for the image registry, you must: Identify the configured provider; Obtain an OpenShift cluster login with administrator permissions; Note: Unless directed otherwise, run the following commands in the CSAH node as user core.
Image Push Errors with Scaled Registry Using Shared NFS Volume. Bug 1575410 - OpenShift 3.9 glusterfs_registry with CNS fails on openshift.common.ip get_facts on hosted-install 2. attach the PVC to the registry. Azure Red Hat OpenShift provides a flexible, self-service deployment of fully managed OpenShift clusters.