This repository provides Helm charts to deploy the Hammerspace CSI driver in a Kubernetes cluster.
The chart installs both the Controller and Node plugins, and supports configuration of timeouts, retry intervals.
Replace
<GITHUB_PAGES_URL>with your GitHub Pages URL whereindex.yamlis hosted (e.g.,https://hammer-space/csi-plugin.github.io/deploy/helm/).
helm repo add hscsi https://hammer-space/csi-plugin.github.io/deploy/helm/
helm repo update
helm install my-hammerspace-csi hscsi/hammerspace-csi --version 1.2.8You can override default settings by creating a custom values.yaml. Example:
# values.yaml (example)
controller:
replicaCount: 2
resources:
requests:
cpu: "200m"
memory: "512Mi"
limits:
cpu: "1"
memory: "1Gi"
node:
# Tolerate control-plane nodes if needed
tolerations:
- key: "node-role.kubernetes.io/control-plane"
operator: "Exists"
effect: "NoSchedule"
helm install hscsi hscsi/hammerspace-csi \
--namespace kube-system \
--create-namespace \
-f values.yamlAlternatively, override values inline:
helm install hscsi hscsi/hammerspace-csi \
--namespace kube-system \
--create-namespace \
--set controller.replicaCount=2kubectl get pods -n kube-system -l app.kubernetes.io/name=hscsi
kubectl get csidrivers | grep hammerspace || truehelm upgrade hscsi -n kube-system -f values.yamlhelm uninstall hscsi -n kube-system| Key | Type | Description |
|---|---|---|
controller.replicaCount |
int | Number of controller replicas |
controller.resources |
map | Requests/limits for controller pods |
node.tolerations |
list | Tolerations for node daemonset |
For all options, see
values.yamlin the chart.
- Pods stuck in ImagePullBackOff: Verify image registry access and tag in the chart values.
- "csi-driver" not found: Run
helm repo updateand check that your<GITHUB_PAGES_URL>/index.yamlis accessible. - No nodes provisioned: Check node plugin DaemonSet tolerations/affinity and that nodes can reach the NFS endpoints.
- Helm: https://helm.sh/docs/
- Kubernetes CSI: https://kubernetes-csi.github.io/docs/