# CSI Drivers

## CSI Drivers and Snapshot capabilities

Please refer to the [Kubernetes CSI community page](https://kubernetes-csi.github.io/docs/drivers.html) that lists almost all CSI drivers available along with the features that they support (snapshot, volume expansion etc.)

{% hint style="warning" %}
The **snapshot** feature must be supported by the CSI driver to be able to function with Trilio for Kubernetes
{% endhint %}

## Sample CSI Drivers

If your environment does not support a CSI driver with snapshot functionality, a few sample CSI drivers along with instructions to install and configure are provided below. These CSI drivers can be leveraged for evaluating Trilio for Kubernetes.

## Amazon Web Services EBS CSI Driver

If your Kubernetes cluster is running with Amazon Web Services, the EBS CSI Driver can be leveraged for persistent volume storage.

Please follow the steps to install and AWS EBS CSI Driver from [GitHub](https://github.com/kubernetes-sigs/aws-ebs-csi-driver)

## Google Cloud Platform GCE CSI Driver

If your Kubernetes cluster is running within Google Cloud, the Google Compute Engine CSI driver can be leveraged for persistent volume storage.

Please follow the steps to install the GCE CSI Driver from [GitHub](https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver)

## Ceph CSI through Rook Operator

Rook is one of the Operators that is deployed through OpenShift Container Storage (OCS) operator. However, the snapshot capabilities are not enabled if installed via the OCS operator.

Therefore, to leverage Ceph CSI with snapshot capabilities as persistent storage, install the Rook based operator via the [Rook Operator](https://rook.io/docs/rook/latest/Getting-Started/quickstart/) page.