Is there any workaround available to the best of your knowledge? Yes.  Workaround #1 For the PVC in a pending state, we can define the storage class in the yaml spec. Once the storage class is defined, the PVC goes into a `Bound` state and the pod subsequently starts running successfully. Workaround #2 (1) Currently I have no default storage class leading to the PVC to go into a pending state ~~~ NAME      PROVISIONER       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE gp2-csi   ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   4d2h gp3-csi   ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   4d2h NAME                                  STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE postgredb-tekton-results-postgres-0   Pending                                                     <unset>                 59 NAME                      READY   AGE tekton-results-postgres   0/1     59m ~~~ (2) Find the owner of the statefulset ~~~ $ oc get sts tekton-results-postgres -oyaml -n openshift-pipelines | yq .metadata.ownerReferences - apiVersion: operator .tekton.dev/v1alpha1   blockOwnerDeletion: true   controller: true   kind: TektonInstallerSet   name: result-pre-rzl59   uid: be763b3f-21cf-45b4-a7d3-a5a905de413c ~~~ (3) Edit the owner of the statefulset ~~~ $ oc edit tektoninstallerset result-pre-rzl59 -n openshift-pipelines <removed- for -space>       volumeClaimTemplates:         - metadata:                       creationTimestamp: null           name: postgredb             spec:                           storageClassName: <storage- class- name> <--- define a storageclass           accessModes:                  - ReadWriteOnce               resources:                      requests:                       storage: 1Gi            status: {}                status:                         availableReplicas: 0          replicas: 0     <removed- for -space> ~~~ (4) Delete the sts and the corresponding PVC ~~~ $ oc delete sts tekton-results-postgres -n openshift-pipelines $ oc delete pvc postgredb-tekton-results-postgres-0 -n openshift-pipelines ~~~ (5) Verify that the PVC and sts are recreated. In my cluster I defined gp3-csi as the storageclass. ~~~ NAME                      READY   AGE tekton-results-postgres   1/1     18s NAME                                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE postgredb-tekton-results-postgres-0   Bound    pvc-4de5fb21-5d3a-4fa4-98dd-a4bfb8ab9f11   1Gi        RWO            gp3-csi        <unset>                 21s ~~~