#1591 Request to create a PV on cloud-softwarefactory namespace
Closed: Fixed by arrfab. Opened by mhuin.

This is a followup to https://pagure.io/centos-infra/issue/1578 (I couldn't update this issue as other priorities piled up and I apologize for that)

Could you create a new PV on the cloud-softwarefactory namespace for us?

name; size; labels; accessModes

sf-gateway-data;1Gi;app=sf|run=gateway; ReadWriteOnce

Also what is the name of the storageClass you are using to create the PVs? I need it to test that the ones you created in the previous issue can be used by our deployment.

Thanks!


Metadata Update from @arrfab:
- Issue tagged with: centos-ci-infra, feature-request, medium-gain, medium-trouble

@mhuin : we don't have any storageClass for our provisioned PVs as it's "user provisioned" and so just basically NFS under the hood (Amazon EFS)

Metadata Update from @arrfab:
- Issue assigned to arrfab

BTW, a new PV was created and you can use these for your PVC :

  capacity:
    storage: 1Gi
  claimRef:
    name: sf-gateway-data
    namespace: cloud-softwarefactory

Metadata Update from @arrfab:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

I'm asking because our application requires a storage class name to provision the PersistentVolumeClaims. I fear that if I create a PVC with an incorrect class this might fail?

Based on official documentation, it seems the PVC can be created with empty storageClassName :
https://docs.openshift.com/container-platform/4.15/storage/persistent_storage/persistent-storage-nfs.html#persistent-storage-nfs-provisioning_persistent-storage-nfs

@mhuin : as the new PV is in place, can we just close this request ?

Yes, let's. I am working on supporting empty storageClassName in our application. Thanks!

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata