BMC Helix IT Operations Management (ITOM) OnPrem Deployment: How to manually test if PersistentVolumeClaim(PVC) is getting bound to storage or not?

Please follow the below steps:

1. Get the storage class name:

For Kubernetes cluster execute:

kubectl get StorageClasses

For OpenShift cluster:

oc get StorageClasses

Example:

[root@controllerNode-example ~]# kubectl get StorageClasses
NAME         PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
nfs-client   cluster.local/nfs-subdir-external-provisioner   Delete          Immediate           true                   36d

2. Create test PersistentVolumeClaim(PVC)

- vi testpvc.yaml
- copy and paste the following. Make sure to change the storage class name accordingly

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc1
spec:
  storageClassName: <storage_class_name>
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 1Gi

- For Kubernetes cluster execute:

kubectl apply -f testpvc.yaml

- For OpenShift cluster:

oc apply -f testpvc.yaml

3. Check PVC status:

oc get pvc
kubectl get pvc

Example:

[root@controllerNode-example~]# kubectl get pvc
NAME                                                          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
pvc1                                              Bound    pvc-64c32c7a-7ce4-4a55-a787-d366d80d7afd   1Gi        RWO            nfs-client     36d

If the PVC is still in the pending state, please validate storage class supports the storage read-write type that is required by:

BMC Helix IT Operations Management deployment - PersistentVolumeClaim (PVC) requirements
BMC Helix Service Management Deployment - PersistentVolumeClaim (PVC) requirements