NFS provisioner and registry volume not created when HA-bastion is used

[MaartenKreuger]

When the bastion host cluster is created by setting the count to 2, the NFS image persistent volume is not created automatically, but also the nfs-provisioner storage class is not created. The following is a workaround: in: ocp4-helpernode/templates/checker.sh.js

cat > registry-pv.yaml <<EOF apiVersion: v1 kind: PersistentVolume metadata: name: registry-pv spec: capacity: storage: 100Gi accessModes: - ReadWriteMany persistentVolumeReclaimPolicy: Retain nfs: path: /export/registry server: nfsserver.mydomain.com EOF oc apply -f registry-pv.yaml

cat > registry-pvc.yaml <<EOF kind: PersistentVolumeClaim apiVersion: v1 metadata: name: registry-pvc namespace: openshift-image-registry spec: accessModes: - ReadWriteMany resources: requests: storage: 100Gi volumeName: registry-pv EOF oc apply -f registry-pvc.yaml

oc patch configs.imageregistry.operator.openshift.io cluster --type=json -p '[{"op": "remove", "path": "/spec/storage/emptyDir" }]' oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"storage":{"pvc":{ "claim": "registry-pvc"}}}}'

I would expect the primary bastion to be configured with a registry export. It's not highly available of course, so we would need to replace it with a Spectrum Scale based export. The extra surprise was that the nfs-provisioner storageclass was not configured, making adding the PVC problematic. Please fix.