Skip to main content
Crusoe Support Help Center home page
Crusoe

How-To Upgrade Crusoe CSI Driver in CMK Cluster

Apeksha Khilari
Apeksha Khilari
Updated

Last Updated: Nov 12, 2025

Introduction

Crusoe provides a growing suite of add-ons and plugins designed to extend the functionality of Crusoe Managed Kubernetes (CMK) clusters. One key add-on is the Container Storage Interface (CSI) driver, which allows workloads within your cluster to create and manage supported Crusoe disk types as PersistentVolumes. Currently, the CSI driver supports both Persistent Disks and Shared Disks.

This page guides you through the steps to upgrade the CSI driver in your cluster. 

Note: It is the user's responsibility to periodically update the add-ons in their cluster to ensure continued compatibility, performance, and access to the latest features. During the upgrade process, you may see intermittent issues with volume attachment, detachment, mounting, or creation until the new CSI pods are fully up and running.

Prerequisites

  • Access to the Crusoe CLI or Crusoe Console
  • Valid Crusoe authentication credentials
  • An existing Crusoe Managed Kubernetes (CMK) cluster with Crusoe CSI driver installed
  • Helm

Step-by-Step Instructions

Note: The Crusoe CSI Driver is only supported on Crusoe Managed Kubernetes (CMK). Other configurations are supported on a best-effort basis.

  1. Ensure the Crusoe CSI driver Helm repo is installed and up-to-date
    • Check if the CSI driver chart already exists:

      $ helm repo list | grep csi-driver              
      
      crusoe-csi-driver       https://crusoecloud.github.io/crusoe-csi-driver-helm-charts/charts    
    • If the Helm repo is already present, update it to the latest version:

      $ helm repo update crusoe-csi-driver
      
      Hang tight while we grab the latest from your chart repositories...
      ...Successfully got an update from the "crusoe-csi-driver" chart repository
      Update Complete. ⎈Happy Helming!⎈
      
    • If the Helm repo is absent, add it:

      $ helm repo add crusoe-csi-driver https://crusoecloud.github.io/crusoe-csi-driver-helm-charts/charts
      
      "crusoe-csi-driver" has been added to your repositories
    • Find the latest available Helm chart version:

      $ helm search repo crusoe-csi-driver
      
      NAME                                    CHART VERSION   APP VERSION     DESCRIPTION                                 
      crusoe-csi-driver/crusoe-csi-driver     0.8.0           v0.3.2          A Helm chart for the Crusoe Cloud CSI Driver
      crusoe-csi/crusoe-csi-driver            0.7.0           v0.3.0          A Helm chart for the Crusoe Cloud CSI Driver
      csi-driver/crusoe-csi-driver            0.7.0           v0.3.0          A Helm chart for the Crusoe Cloud CSI Driver
  2. Create override_values.yaml for the secret name and paths override 
    • Create a YAML file override_values.yaml with the following contents (do not replace any values):

      crusoe:
        secrets:
          crusoeApiKeys:
            # The Crusoe CSI Driver requires access to the Crusoe API in order to manage and mount Crusoe Storage Disks.
            # It is expected that the secret will contain two keys at accessKeyPath and secretKeyPath containing
            # the base64 encoded access key and secret key respectively.
            secretName: "crusoe-secrets"
            accessKeyPath: "CRUSOE_ACCESS_KEY"
            secretKeyPath: "CRUSOE_SECRET_KEY"
  3. Upgrade the helm release by supplying override values
    • Note down the name of the CSI driver release:

      $ helm list -n crusoe-system 
       
      NAME             	    NAMESPACE    	REVISION	    UPDATED                             	STATUS  	CHART                  	APP VERSION
      crusoe-csi-driver       crusoe-system   1               2025-09-18 05:08:23.328386132 +0000 UTC deployed    crusoe-csi-driver-0.6.2 v0.2.1
    • Upgrade the Helm release to the latest chart version found in Step 1:

      $ helm upgrade crusoe-csi-driver crusoe-csi-driver/crusoe-csi-driver --version 0.8.0 -f override_values.yaml -n crusoe-system 
      
      Release "crusoe-csi-driver" has been upgraded. Happy Helming!
      NAME: crusoe-csi-driver
      LAST DEPLOYED: Thu Sep 18 18:35:32 2025
      NAMESPACE: crusoe-system
      STATUS: deployed
      REVISION: 2
      TEST SUITE: None
  4. Verify the upgrade
    • Verify the Helm release is installed with the latest chart version:

      $ helm list -n crusoe-system 
      
      NAME                    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
      crusoe-csi-driver       crusoe-system   2               2025-09-18 18:35:32.633326 -0700 PDT    deployed        crusoe-csi-driver-0.8.0 v0.3.2
    • Verify the CSI driver pods are up and running:

      $ kubectl get pods -n crusoe-system | grep csi
      
      crusoe-csi-driver-fs-controller-7975568785-kpv6s   5/5     Running   0          2m41s
      crusoe-csi-driver-fs-node-dwjvr                    3/3     Running   0          2m42s
      crusoe-csi-driver-fs-node-fgf7r                    3/3     Running   0          2m34s
      crusoe-csi-driver-fs-node-nxxct                    3/3     Running   0          2m37s
      crusoe-csi-driver-ssd-controller-5f8c6cb8b-zclsk   5/5     Running   0          2m41s
      crusoe-csi-driver-ssd-node-459c6                   3/3     Running   0          2m37s
      crusoe-csi-driver-ssd-node-4dbx2                   3/3     Running   0          2m41s
      crusoe-csi-driver-ssd-node-5tb2s                   3/3     Running   0          2m34s

Related to

Was this article helpful?

0 out of 0 found this helpful

Still need help?

Our support team is ready to assist you with any questions.

Have more questions? Submit a request

Recently Viewed

Comments

0 comments

Article is closed for comments.