Chuck Fouts

@Numblesix, thanks for adding the detail that this was only seen during an OCP update.

Hi @frasmarco, we are currently tracking this feature request on our roadmap. Thanks for inquiring on this issue as it provides us with a better idea of interest in this...

Hi @pjos and @matalve, The Trident team just finished investigating this issue and found that if NAE is enabled for your aggregate then data at rest is encrypted for every...

Hi @matalve, From our testing we did not observe that NAE encryption could be disabled. We did observe that setting the encryption flag as "true" overrides NAE enabled aggregates with...

@matalve and @arndt-netapp, I need to apologize as @arndt-netapp's original post is correct. The issue is that current Trident versions send a "false" flag for the encryption value when a...

@scaleoutsean, ARM64 support is on the Trident roadmap and will be supported in a future release.

Hi @tonyskapunk, The tridentctl command does need to inspect the cluster to determine the correct CSI snapshotter sidecar version to report. We expect that there will be additional checks in...

@wonderland and @tonyskapunk, access to the K8S cluster is needed to determine the correct version of the CSI snapshotter sidecar that is needed. The snapshotter version is determined based on...

Hi @uberspot, You may want to contact [NetApp support](https://mysupport.netapp.com/site/info/find-support) and open a support case so that we can help you further. What seems to be happening is that Trident has...

@ffilippopoulos we've discussed this issue and it seems like your problem determination is spot on so far. We are wondering about the workflow you are using that is causing the...