Storage Solution - Getting Started

In Kubernetes you cannot write data directly to the underlying physical disk. You need to use a Volume Provisioner for making use of your local, network, shared network or cloud storage.

Local storage

For a single node/simplex, staging, or QA environment you can use local node storage with any of the available local path provisioners.

OpenEBS Local PV

RECOMMENDED

OpenEBS Local PV makes use of HostPath for dynamic provisioning. See OpenEBS PV documentation for the usecases and pros/cons. This option may be used for CX for the following use cases. See Setup OpenEBS for Local Volume Provisioning for installation/configurations of OpenEBS.

Simplex deployment where high availability is not required.
High availability architecture using application level replication. (works with Control Plane HA only

Cloud native storage

You can use any of the CNCF cloud-native storage for dynamic provisioning of persistent volumes. Expertflow team has tested the solution with the following.

vSAN/vSphere	If you are using VMWare infrastructure, this could be your first choice for provisioning persistent storage volumes.
NFS	If you already have NFS provisioned in your environment, consider using this option. See NFS Storage Service to setup NFS as your cloud native storage.
Rook/Ceph	Ceph based on-prem cloud native storage solution for Kubernetes. Complex to setup with dedicated resource, works well with Kubernetes. See rook/Ceph quickstart guide for further details.
Longhorn	Cloud Native Storage solution for Kubernetes by Rancher. Requires dedicated resources. See Longhorn Deployment Guide for setting up Longhorn as the cloud-native storage.

For a complete list of available storage (CSI) drivers that can be used with Kubernetes, see https://kubernetes-csi.github.io/docs/drivers.html.

Next Steps

CX Deployment on Kubernetes