content_image/1001225.jpg content_image/1001224.jpg
<img src='content_image/1001225.jpg'>

==> 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 

<img src='content_image/1001224.jpg'>

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) 

