We validated the deployment that is described in this guide using Unity 380F software version 5.0.0.0.5.116. The following code snippet shows the Unity 380F NAS server and NFS share details:
Unitynfs
Description:
NAS Server:
unitynas
File System:
unitynfs
Local Path:
/unitynfs/
Default Access:
Read/Write, allow Root
Hosts:
0
All Export paths:
100.82.46.8:/unitynfs
Prerequisites
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.
- Create a PV file nfsimageregpv.yml using the following content and modifying the path and server values for your environment:
apiVersion: v1
kind: PersistentVolume
metadata:
name: nfs-image-registry
namespace: openshift-image-registry
spec:
capacity:
storage: 100Gi
accessModes:
- ReadWriteMany
nfs:
path: /unitynfs
server: 100.82.46.8
persistentVolumeReclaimPolicy: Retain
- Apply the CR you created in Step 3 of Htpasswd authentication:
oc apply -f nfsimageregpv.yml
- Edit the registry configuration to use the newly created PV:
- oc edit configs.imageregistry.operator.openshift.io
- Scroll down to Storage and add the following lines:
- Save the file, and then quit by running :wq
The image-registry cluster operator is updated and a new PV claim is created using the PV that we created using Unity NFS storage.
