Chuck Fouts

Hi @yajith, The default value of 1 second for the readinessProbe and livenessProbe should be more than enough time to respond to Kubelet, which is running on the same K8S...

Hi @Numblesix, we test with OCP and have not run into this issue. Also, we haven't received confirmation from another customer that they have encountered this issue. Is there any...

Hi @uberspot, Trident uses the lsscsi binary to collect information that is useful when debugging iSCSI related issues. This binary isn't available in CoreOS but does not prevent Trident from...

Hi @rakkatta424, We recommend that you open a NetApp support case to help you out with this upgrade issue. If you want to try and solve this issue via this...

Hi @bigg01, You should check out NetApp's [Project Astra](https://cloud.netapp.com/project-astra). Talk to your NetApp account team if you are also interested in having Metro Cluster support in Project Astra!

Hi @nheinemans, The Trident Operator doesn't have access to the K8S worker nodes where the Trident Node Plugin is running. With Trident v23.01, iSCSI self-healing logic was added to handle...

@nheinemans, thanks for the additional information. @ntap-arorar looked at the issue and thinks to could be one of the following possibilities: 1. One of the session paths was in a...

Hi @eselvam, We verified again that Trident v22.07 is able to mount a NAS volume when using OCP 4.10. We do not think the mount issue that you were experiencing...

Hi @rsjonte, Thanks for the update and it is good to hear that you've found a work around. At this time, Trident doesn't test for FIPS 140-2 compliance and uses...

Hi @rsjonte, Thanks again for reporting the workaround on this issue. We will continue to track customer demand for Trident to support OCP with FIPS enabled. Until FIPS is supported...