Enhance csi-snapshot-controller README with troubleshooting guidance for CrashLoopBackOff issues and update kustomization.yaml to include deployment patch. This improves user experience and deployment reliability.
This commit is contained in:
@@ -14,3 +14,17 @@ kubectl -n kube-system rollout status deploy/snapshot-controller --timeout=120s
|
||||
```
|
||||
|
||||
After this, create or label a **VolumeSnapshotClass** for Longhorn (`velero.io/csi-volumesnapshot-class: "true"`) per `clusters/noble/bootstrap/velero/README.md`.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If **`snapshot-controller`** is **CrashLoopBackOff** with exit **255** / **1**, check previous logs:
|
||||
|
||||
```bash
|
||||
kubectl -n kube-system logs deploy/snapshot-controller --previous --tail=80
|
||||
```
|
||||
|
||||
Typical causes:
|
||||
|
||||
1. **Volume Snapshot CRDs missing or wrong version** — re-apply: `kubectl apply -k clusters/noble/bootstrap/csi-snapshot-controller/crd`
|
||||
2. **Volume group snapshot APIs** — this repo installs **GA** `VolumeSnapshot*` CRDs only. The controller overlay sets **`--feature-gates=CSIVolumeGroupSnapshot=false`** so the binary does not expect **VolumeGroupSnapshot*** CRDs.
|
||||
3. **RBAC** — re-apply the controller kustomize (includes `rbac-snapshot-controller.yaml`).
|
||||
|
||||
Reference in New Issue
Block a user