==> v1beta1/DaemonSet NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE portworx 3 3 0 3 0 <none> 0s ==> v1/Pod(related) NAME READY STATUS RESTARTS AGE portworx-6qlvp 0/1 ContainerCreating 0 0s portworx-c4h4t 0/1 ContainerCreating 0 0s portworx-p86qn 0/1 ContainerCreating 0 0s stork-scheduler-679f999679-5gbt7 0/1 ContainerCreating 0 0s stork-scheduler-679f999679-jq6gp 0/1 ContainerCreating 0 0s stork-scheduler-679f999679-w5mv5 0/1 ContainerCreating 0 0s stork-86bb9cb55d-467wr 0/1 ContainerCreating 0 0s stork-86bb9cb55d-969vf 0/1 ContainerCreating 0 0s stork-86bb9cb55d-khwrv 0/1 ContainerCreating 0 0s portworx-null-sc kubernetes.io/portworx-volume 0s portworx-db2-sc kubernetes.io/portworx-volume 0s portworx-db-sc kubernetes.io/portworx-volume 0s portworx-shared-sc kubernetes.io/portworx-volume 0s NOTES: Your Release is named "portworx" Portworx Pods should be running on each node in your cluster. Portworx would create a unified pool of the disks attached to your Kubernetes  nodes. No further action should be required and you are ready to consume Portworx Volumes  as part of your application data requirements. For further information on usage of the Portworx in creating Volumes please refer https://docs.portworx.com/scheduler/kubernetes/preprovisioned-volumes.html For dynamically provisioning volumes for your Stateful applications as they run on  Kubernetes please refer https://docs.portworx.com/scheduler/kubernetes/dynamic-provisioning.html Want to use Storage Orchestration for hyperconvergence, Please look at STork here.  (NOTE: This isnt currently deployed as part of the Helm chart) Chapter 4. Managing persistence in IBM Cloud Private  145 ==> v1/StorageClass stork-snapshot-sc stork-snapshot 0s ==> v1/ServiceAccount NAME SECRETS AGE px-account 1 0s stork-scheduler-account 1 0s stork-account 1 0s ==> v1/ClusterRoleBinding NAME AGE node-role-binding 0s stork-scheduler-role-binding 0s stork-role-binding 0s