Operations on KlustreFS

Label Lustre-capable nodes

Mon, 01 Jan 0001 00:00:00 +0000

The default klustre-csi-static storage class restricts scheduling to nodes labeled lustre.csi.klustrefs.io/lustre-client=true. Use this runbook whenever you add or remove nodes from the Lustre client pool.

Requirements

Cluster-admin access with kubectl.
Nodes already have the Lustre client packages installed and can reach your Lustre servers.

Steps

Identify nodes that can mount Lustre
```
kubectl get nodes -o wide
```
Cross-reference with your infrastructure inventory or automation outputs to find the node names that have Lustre connectivity.

Update the Klustre CSI image

Mon, 01 Jan 0001 00:00:00 +0000

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-secret or 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 the nodeImage key with the new tag:

Collect diagnostics

Mon, 01 Jan 0001 00:00:00 +0000

When reporting an issue, provide the following artifacts so maintainers can reproduce the problem.

1. Capture pod logs

kubectl logs -n klustre-system daemonset/klustre-csi-node -c klustre-csi --tail=200 > klustre-csi.log
kubectl logs -n klustre-system daemonset/klustre-csi-node -c node-driver-registrar --tail=200 > node-driver-registrar.log

If a specific pod is failing, target it directly:

kubectl logs -n klustre-system <pod-name> -c klustre-csi --previous

2. Describe pods and daemonset

kubectl describe daemonset klustre-csi-node -n klustre-system > klustre-csi-daemonset.txt
kubectl describe pods -n klustre-system -l app.kubernetes.io/name=klustre-csi > klustre-csi-pods.txt

3. Export relevant resources

kubectl get csidriver lustre.csi.klustrefs.io -o yaml > csidriver.yaml
kubectl get storageclass klustre-csi-static -o yaml > storageclass.yaml
kubectl get configmap klustre-csi-settings -n klustre-system -o yaml > configmap.yaml

Remove sensitive data (e.g., registry credentials) before sharing.