14 lines
1.0 KiB
Plaintext
14 lines
1.0 KiB
Plaintext
|
Your Release is named {{ .Release.Name | quote }}
|
||
|
|
|
||
|
|
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, refer to following doc pages.
|
||
|
|
|
||
|
|
- For dynamically provisioning volumes: https://docs.portworx.com/scheduler/kubernetes/dynamic-provisioning.html
|
||
|
|
- For preprovisioned volumes: https://docs.portworx.com/scheduler/kubernetes/preprovisioned-volumes.html
|
||
|
|
- To use Stork (Storage Orchestration Runtime for Kubernetes) for hyperconvergence and snapshots: https://docs.portworx.com/scheduler/kubernetes/stork.html
|
||
|
|
- For stateful application solutions using Portworx: https://docs.portworx.com/scheduler/kubernetes/k8s-px-app-samples.html
|
||
|
|
- For interactive tutorials on using Portworx on Kubernetes: https://docs.portworx.com/scheduler/kubernetes/px-k8s-interactive.html
|