scaeloutSean

This issue has a more pronounced effect on Element OS (probably E-Series too) because the maximum number of snapshots on these platforms is lower than ONTAP: while on ONTAP the...

I use Option 1 when I have to, because I haven't found a way to "reanimate" volumes whose backend went down and then came up. Only, unlike in your Option...

> I have tried to add the param into the storage class "csi.storage.k8s.io/fstype" = "nfs" however this does not seem to be supported by the storage provisioner That's a claim....

I completed the rest, basically there's just other 2 tricky places: - find amd64 and replace it with arm64 in setup/*.yaml - remove the entire NeApp autosupport container section in...

@skuethe you're likely looking for an officially supported version, but if you want to experiment with current version, give it a try... I've been running various releases (from v21.01 to...

@christianjedroCDT, I somehow got your comment asking about additional details via email (Github email notifications), but I can't see it here. Yes, I documented the details (above) but even even...

`tridentctl version` also requires a cluster to run (in addition to not actually giving version info about the binary `tridentctl` itself even when it runs online). That doesn't mean it...

Thanks, @adkerr! In that case `--client` would work for me if it was a way to get a list of supported `images`.

> ******************mountpoint /var/lib/kubelet/pods/ea842b1b-3534-43e5-8a83-efcef63d41b0/volumes/kubernetes.io~csi/pvc-******************/mount: fork/exec /netapp/mount: exec format error You're clearly using an x86 executable. As mentioned [here](https://github.com/NetApp/trident/issues/534#issuecomment-784747931) you need to replace all amd64 base with arm64 base images. Which is...

@vveeregandha are you building on x86_64 or ARM64 (natively)? On x86_64 you need a functioning cross-patform build toolkit. Secondly, have you got that suggestion in the steps to hard-code ARM64...