---
title: "Create a Helm Chart Configuration File for VAST COSI Driver"
slug: "create-a-helm-chart-configuration-file-for-vast-cosi-driver-2-5"
updated: 2026-11-04T01:39:29Z
published: 2026-11-04T01:39:29Z
canonical: "docs.vastdata.com/create-a-helm-chart-configuration-file-for-vast-cosi-driver-2-5"
---

> ## 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.

# Create a Helm Chart Configuration File for VAST COSI Driver

The driver's Helm chart configuration file lets you override default installation settings provided in the chart with parameters that are specific to your environment.

The configuration file is a YAML file typically named `values.yaml`, although you can use any arbitrary name for it.

- [Create a Configuration File](/develop/docs/create-a-helm-chart-configuration-file-for-vast-cosi-driver-2-5#create-a-configuration-file)
- [Verify the Configuration File](/develop/docs/create-a-helm-chart-configuration-file-for-vast-csi-driver-2-5#verify-the-configuration-file)

## Create a Configuration File

Create a YAML file as follows (see also the example below:

```plaintext
BucketClassDefaults:
  secretName: "<secret>"
  endpoint: "<endpoint>"
  verifySsl: true|false
  sslCertsSecretName: "<SSL secret>"

bucketClasses:
  <bucket class name 1>:
    <option 1>
    <option 1>
    ...
    <option n>
  <bucket class name 2>:
    <option 1>
    <option 1>
    ...
    <option n>
 ...
  <bucket class name n>:
    <option 1>
    <option 1>
    ...
    <option n>
```

In the YAML file:

1. Set session options:

  - `secretName: "&lt;secret&gt;"` (required): Specify the Kubernetes secret with VMS user credentials to be used by the VAST COSI Driver. The secret must include the VMS user's username and password. For more information, see [Create a Kubernetes Secret with VMS User Credentials for VAST COSI Driver](/develop/docs/create-a-kubernetes-secret-with-vms-user-credentials-for-vast-cosi-driver-2-5).
  - `endpoint: "&lt;endpoint&gt;"` (required): Enter the VAST Cluster management hostname.
  - `verifySsl: true|false` (optional): Specify `true` to enable [SSL encryption](/develop/docs/configuring-ssl-encryption-for-vast-cosi-driver-2-5) for the connection to the VAST cluster. If set to `false` or not specified, SSL encryption is disabled.

> [!TIP]
> **Tip**
> 
> When enabling SSL encryption, either upload a CA-signed SSL certificate to the VAST cluster (see the procedure in the *VAST Cluster Administrator's Guide*), or [supply](/develop/docs/en/configuring-ssl-encryption-for-vast-cosi-driver-1) a self-signed SSL certificate to the driver. The latter can be done either via the `sslCertsSecretName` option, or using `--set-file sslCert` on the Helm chart installation command.
  - `sslCertsSecretName: "&lt;SSL secret&gt;"` (optional): Specify the Kubernetes secret that contains the self-signed SSL certificate to be used to secure communications between VAST COSI Driver and the VAST cluster. For more information, see [Configuring SSL Encryption for VAST COSI Driver](/develop/docs/configuring-ssl-encryption-for-vast-cosi-driver-2-5).
2. Set bucket class options:

  - `&lt;bucket class name&gt;` (required): Provide a name to identify the bucket class.

> [!NOTE]
> **Note**
> 
> Define at least one bucket class.
  - `&lt;option 1&gt;`...`&lt;option n&gt;`: Specify parameters to be used when provisioning storage for buckets with this bucket class. For information on supported options, see [Bucket Class Option Reference](/develop/docs/en/bucket-class-option-reference-1).

For each bucket class, the required options are:

```plaintext
bucketClasses:
  <bucket class name>:
    storagePath: "<path>"
    vipPool: "<virtual IP pool name>"
    viewPolicy: "<view policy>"
```
3. (Optional) Configure registration of the VAST COSI Driver with `kubelet`:

  - `kubeletPath: "&lt;your kubelet root directory&gt;"` (optional): Add this option if you are going to run VAST COSI Driver on a Kubernetes cluster where the kubelet root directory is not `/var/lib/kubelet`.

The following snippet shows a sample configuration file for VAST COSI Driver:

```plaintext
BucketClassDefaults:
  secretName: "vast-mgmt"
  endpoint: "my.endpoint"

bucketClasses:
  vastdata-bucket:
    storagePath: "/cosi/buckets"    
    vipPool: "vippool-1"
    viewPolicy: "cosi"
```

## Verify the Configuration File

You can verify the newly created chart configuration file by running the following command:

```plaintext
helm template <release name> <repo>/<chart> -f <filename>.yaml -n <namespace>
```

Where:

- `&lt;release name&gt;` identifies the release being deployed.
- `&lt;repo&gt;` is the name of the [VAST driver Helm repository](/develop/docs/add-the-helm-repository-for-vast-cosi-driver-2-5).
- `&lt;chart&gt;` is the name of the [VAST driver Helm chart](/develop/docs/install-the-vast-cosi-driver-helm-chart-2-5) (`vastcosi`).
- `&lt;filename&gt;.yaml` is the VAST driver chart configuration file.
- `&lt;namespace&gt;` (optional) determines the Kubernetes namespace to which the release is deployed. If this parameter is not specified, the `default` namespace is used. Otherwise, [create](/develop/docs/create-a-kubernetes-namespace-for-vast-cosi-driver-2-5) a custom namespace prior to installing the VAST driver chart.

For example:

```plaintext
helm template cosi-driver vastcosi/vastcosi -f values.yaml
```