After deleting deployment, pvc on ROSA STS kind cluster volume still remains forever in cluster with Released status

4.19.0-0.nightly-2025-05-28-035647    

Always

1. Create ROSA STS kind cluster
ex: https://github.com/openshift/release/pull/64623#issuecomment-2914825579
2. Do setup for AWS EFS Cross account support as mentioned in doc. 
ttps://docs.google.com/document/d/1-c87alz1p4Q6xUxIEx-aogkocZpaXeLXbN3HVrxLvPo/edit
3. Create efs sc, pvc, dep, Write some data inside volume
4. Delete the deployment, pvc. 
5. Check the pv resource 

The pv pvc-a16618ad-d351-46eb-b22a-019788af389a remains in cluster forever with Released status.

oc get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                                                        STORAGECLASS          VOLUMEATTRIBUTESCLASS   REASON   AGE
pvc-505ac199-b9da-4c3a-aa1d-7af982270c1a   100Gi      RWO            Delete           Bound      openshift-monitoring/prometheus-data-prometheus-k8s-0        gp3-customer-kms      <unset>                          6h24m
pvc-5d2aa230-3ffb-4e65-a544-696830aed499   100Gi      RWO            Delete           Bound      openshift-monitoring/prometheus-data-prometheus-k8s-1        gp3-customer-kms      <unset>                          6h20m
pvc-80d75d81-6b45-483b-a6af-439c00af4ce1   10Gi       RWO            Delete           Bound      openshift-monitoring/alertmanager-data-alertmanager-main-1   gp3-customer-kms      <unset>                          6h20m
pvc-a16618ad-d351-46eb-b22a-019788af389a   1Gi        RWX            Delete           Released   testropatil/mypvc-fs                                         efs-crossaccount-sc   <unset>                          23m
pvc-f613a89c-1106-43bf-96d9-75e55fce17da   10Gi       RWO            Delete           Bound      openshift-monitoring/alertmanager-data-alertmanager-main-0   gp3-customer-kms      <unset>                          6h24m

The pv should not be present after deleting deployment, pvc. 

Since this is STS kind cluster, the installation steps mentioned in doc are not correct, 
we need to mention ROLE ARN value while installing OperatorGroup, Subscription which we created earlier 
og-sub.yaml
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  generateName: openshift-cluster-csi-drivers-
  namespace: openshift-cluster-csi-drivers
spec:
  namespaces:
  - ""
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: aws-efs-csi-driver-operator
  namespace: openshift-cluster-csi-drivers
spec:
    channel: stable
    name: aws-efs-csi-driver-operator
    source: qe-app-registry
    sourceNamespace: openshift-marketplace
    config:
      env:
      - name: ROLEARN
        value: arn:aws:iam::301721915996:role/ocpe2e-foyxvbro-aws-efs-csi-operator
 
More execution details here: https://issues.redhat.com/browse/STOR-2378?focusedId=27223832&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27223832