---
title: "About VAST COSI Driver"
slug: "about-vast-cosi-driver-2-7"
updated: 2026-11-04T00:37:20Z
published: 2026-11-04T00:37:20Z
canonical: "docs.vastdata.com/about-vast-cosi-driver-2-7"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# About VAST COSI Driver

## Overview of VAST COSI Driver

VAST COSI Driver allows container orchestration frameworks such as Kubernetes to dynamically provision object storage on a VAST cluster using the [Container Object Storage Interface (COSI)](https://container-object-storage-interface.sigs.k8s.io/).

With dynamic provisioning, you do not need to create container-specific volumes. Instead, you deploy a dynamic provisioner and a YAML class definition that specifies the dynamic provisioner and provisioning options. When an application makes a claim for storage, the Kubernetes framework employs the dynamic provisioner to dynamically create a persistent volume. Later, when a containerized application (via its YAML) references this claim, Kubernetes provides the storage to the container.

With VAST COSI Driver, you can:

- [Provision](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#define-bucket-class) buckets based on multiple bucket classes
- [Set](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#set-quotas) quotas on buckets being provisioned
- [Configure](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#configure-lifecycle-rules) lifecycle rules on buckets being provisioned

VAST COSI Driver provides support for the following:

- [SSL encryption](/develop/docs/deploy-vast-cosi-driver-2-7#configure-ssl-encryption-for-vast-cosi-driver) of the connection to the VAST cluster
- [S3 versioned buckets](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#provision-buckets-with-s3-versioning)
- [Externally managed bucket access keys](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#use-externally-managed-bucket-access-keys)
- [Using an existing user account as the bucket owner](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#set-bucket-owner)

VAST CSI Driver capabilities include:

- [Automatic creation](/develop/docs/about-vast-cosi-driver-2-7#automatic-creation-of-view-per-bucket) of a VAST cluster view for each volume being provisioned
- [Leveraging](/develop/docs/about-vast-cosi-driver-2-7#leveraging-trash-folder-access-to-handle-deletions) the VAST cluster's Trash Folder Access functionality to handle deletions
- [Support](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#provision-buckets-on-multiple-vast-cluster-tenants) for multiple VAST cluster tenants
- [DNS-based resolution](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#set-up-dnsbased-virtual-ip-resolution) of virtual IPs
- [Export](/develop/docs/provision-object-storage-with-vast-cosi-driver-2-7#export-connection-parameters-to-environment-variables) of connection parameters to environment variables

## Automatic Creation of View per Bucket

VAST COSI Driver creates a VAST cluster view for each volume or bucket being provisioned. Such a view is automatically deleted when its volume or bucket is deleted.

The views created by VAST COSI Driver can be monitored using VAST cluster's Web UI or CLI.

To control access permissions for storage exposed through these views, VAST COSI Driver uses a view policy that is attached to the view. This is the view policy specified for the bucket class in the VAST COSI Driver's Helm chart configuration file.

## Leveraging Trash Folder Access to Handle Deletions

VAST COSI Driver gains a substantial performance boost during bucket deletions through the use of *Trash Folder Access*, a feature of the VAST cluster described in the *VAST Cluster Administrator's Guide*. The delete request is processed using the VAST REST API's `/folders/delete_folder/` endpoint. This means that the processing takes place locally on the VAST cluster.