Skip to content

scaleway/scaleway-csi

Repository files navigation

Scaleway Block Volume CSI driver

The Scaleway Block Volume Container Storage Interface (CSI) driver is an implementation of the CSI interface to provide a way to manage Scaleway Block Volumes through a container orchestration system, like Kubernetes.

CSI Specification Compatibility Matrix

Scaleway CSI Driver \ CSI Version v1.2.0 v1.6.0 v1.8.0
master branch
v0.1.x
v0.2.x
v0.3.x

Features

Here is a list of features implemented by the Scaleway CSI driver.

Block device resizing

The Scaleway CSI driver implements the resize feature (example for Kubernetes). It allows an online resize (without the need to detach the block device). However resizing can only be done upwards, decreasing a volume's size is not supported.

Raw Block Volume

Raw Block Volumes allows the block volume to be exposed directly to the container as a block device, instead of a mounted filesystem. To enable it, the volumeMode needs to be set to Block. For instance, here is a PVC in raw block volume mode:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-raw-pvc
spec:
  volumeMode: Block
  [...]

At-Rest Encryption

Support for volume encryption with Cryptsetup/LUKS. See more details in examples

Volume Snapshots

Volume Snapshots allows the user to create a snapshot of a specific block volume.

Volume Statistics

The Scaleway CSI driver implements the NodeGetVolumeStats CSI method. It is used to gather statistics about the used block volumes. In Kubernetes, kubelet exposes these metrics.

Block Storage Low Latency

The Scaleway CSI driver is built upon the Block Storage Low Latency Scaleway product. It currently provides volumes with up to 15,000 IOPS. By default, created volumes have 5000 IOPS. To create volumes with higher IOPS, you can set the iops parameter to the requested number of IOPS in your StorageClass. For example:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: my-15k-iops-storage-class
provisioner: csi.scaleway.com
reclaimPolicy: Delete
parameters:
  iops: "15000"

Kubernetes

This section is Kubernetes specific. Note that Scaleway CSI driver may work for older Kubernetes versions than those announced. The CSI driver allows to use Persistent Volumes in Kubernetes.

Kubernetes Version Compatibility Matrix

Scaleway CSI Driver \ Kubernetes Version Min K8s Version Max K8s Version
master branch v1.20 -
v0.1.x v1.17 -
v0.2.x v1.20 -
v0.3.x v1.20 -

Examples

Some examples are available here.

Installation

These steps will cover how to install the Scaleway CSI driver in your Kubernetes cluster, using Helm.

Warning

You should NOT install the Scaleway Block Volume CSI driver in a Scaleway Kubernetes managed cluster (Kapsule / Kosmos) as it is already installed and configured automatically.

Requirements

  • A Kubernetes cluster running on Scaleway instances (v1.20+)
  • Scaleway Project or Organization ID, Access and Secret key
  • Helm v3

Deployment

  1. Add the Scaleway Helm repository.

    helm repo add scaleway https://helm.scw.cloud/
    helm repo update
  2. Deploy the latest release of the scaleway-csi Helm chart.

    helm upgrade --install scaleway-csi --namespace kube-system scaleway/scaleway-csi \
        --set controller.scaleway.env.SCW_DEFAULT_ZONE=fr-par-1 \
        --set controller.scaleway.env.SCW_DEFAULT_PROJECT_ID=11111111-1111-1111-1111-111111111111 \
        --set controller.scaleway.env.SCW_ACCESS_KEY=ABCDEFGHIJKLMNOPQRST \
        --set controller.scaleway.env.SCW_SECRET_KEY=11111111-1111-1111-1111-111111111111

    Review the configuration values for the Helm chart.

  3. You can now verify that the driver is running:

    $ kubectl get pods -n kube-system
    [...]
    scaleway-csi-controller-76897b577d-b4dgw   8/8     Running   0          3m
    scaleway-csi-node-hvkfw                    3/3     Running   0          3m
    scaleway-csi-node-jmrz2                    3/3     Running   0          3m
    [...]

    You should see the scaleway-csi-controller and the scaleway-csi-node pods.

Important

When upgrading an existing installation, you MUST upgrade CRDs before calling helm upgrade command. CRDs are not updated by Helm. See HIP-0011 for details.

helm repo update
helm show crds scaleway/scaleway-csi | kubectl apply --server-side --force-conflicts -f -
helm upgrade --namespace kube-system --reuse-values scaleway-csi scaleway/scaleway-csi

Development

Build

You can build the Scaleway CSI driver executable using the following commands:

make build

You can build a local docker image named scaleway-csi for your current architecture using the following command:

make docker-build

Test

In order to run the tests:

make test

In addition to unit tests, we provide tools to run the following tests:

Contribute

If you are looking for a way to contribute please read the contributing guide

Code of conduct

Participation in the Kubernetes community is governed by the CNCF Code of Conduct.

Reach us

We love feedback. Feel free to reach us on Scaleway Slack community, we are waiting for you on #k8s.

You can also join the official Kubernetes slack on #scaleway-k8s channel

You can also raise an issue if you think you've found a bug.

Packages

No packages published

Contributors 8

Languages