Rohit Arora

@haugom Just want to make sure I understand your requirement correctly. If your requirement is to use an alternate registry for the CSI images, then operator `imageRegistry` option lets you...

> Hi @ntap-arorar > > You are correct. It is the second option and that is why I am asking if this feature could be included in a future release....

A recent commit (scheduled for 21.01.0) https://github.com/NetApp/trident/commit/892e75d8ce216c9d024ce47ca5876ad89c08d312 is a step in this direction. Using the `imageRegistry` option users will be able to replace the `quay.io/k8scsi` portion of the CSI-sidecars.

@roycec Please provide an absolute path to the autosupportImage as well when you are using the `imageRegistry` option. e.g. ``` imageRegistry: localhost:5000/sig-storage tridentImage: localhost:5000/netapp/trident:tag autosupportImage: localhost:5000/netapp/trident-autosupport:tag ```

Hello @Numblesix, Today operator does work with a custom image. Since Trident operator runs as deployment and needs to be up and running before acting on the tprov/torc CR, it...

I would let @gnarl answer your last question.

@lindhe I agree there should be some minimalistic description, however, with TridentBackendConfig (TBC) its difficult to describe each of the fields. If you look at the Trident documentation, you will...

I truly appreciate that you want to provide consistent behaviour with TridentBackendConfig CRD. If I understand your proposal, you want to include this information in the description. Each of Trident's...

The above logs are seen at the time of NodeStageVolume, which means a PV already exists at this point and is bound to a PVC. At the time of NodeStageVolume,...