Update the Klustre CSI image
Roll out a new plugin container image across the daemonset.
Use this guide to bump the Klustre CSI image version (for example, when adopting a new release).
Requirements
- Cluster-admin access.
- The new image is pushed to a registry reachable by your cluster (GHCR or a mirror).
- The
ghcr-secretor equivalent image pull secret already contains credentials for the registry.
Steps
Edit the settings ConfigMap
The manifests and Helm chart both reference
ConfigMap/klustre-csi-settings. Update thenodeImagekey with the new tag:kubectl -n klustre-system edit configmap klustre-csi-settingsExample snippet:
data: nodeImage: ghcr.io/klustrefs/klustre-csi-plugin:0.1.2Save and exit.
Restart the daemonset pods
kubectl rollout restart daemonset/klustre-csi-node -n klustre-systemWatch the rollout
kubectl rollout status daemonset/klustre-csi-node -n klustre-system kubectl get pods -n klustre-system -o wideVerify the running image
kubectl get pods -n klustre-system -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.containerStatuses[0].image}{"\n"}{end}'Confirm all pods now report the new tag.
Optional: clean up old images
If you mirror images, remove unused tags from your registry or automation as needed.
Related topics
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.