Missing documentation on TridentBackendConfig

[makkes]

From the README it is unclear to me what I can configure in a TridentBackendConfig CR. Some examples:

• What can I use for .spec.storageDriverName?
• What is the meaning of .spec.backendName, .spec.networkInterfaces?
• How do I provide credentials? There's .spec.credentials but there's no explanation of the expected format or what that name refers to (I suppose a Secret?).
• What do the values in .spec.storage.* mean? Do they set the behaviour of the storage provisioner? Are they just informational?
• ...

[Shanna-chen]

Hi @makkes

Thank you for your questions and feedback regarding the TridentBackendConfig CR. I have updated the README and sample files to provide more clarity.

I recommend reviewing the updated README and sample files to see if they address your concerns. Please feel free to reach out if you have any further questions or require additional clarification.

[makkes]

Great work, @Shanna-chen. I've been trying to get it working with the updated README all day today but I'm stuck at the controller not being able to login to the QNAP device:

0s (x9 over 4m2s)      Warning   Failed   TridentBackendConfig/XXX   Failed to create backend: problem initializing storage driver 'qnap-iscsi': rpc error: code = Unknown desc = login failed; please check if storage is online

It sounds similar to what's described in #15 but I'm 100% certain I put the correct credentials into the Secret. I verified them by logging into the Web UI with these exact credentials.

This is not directly related to the README but I believe the README is missing a vital part, i.e. explaining what is necessary to be done on the QNAP device prior to being able to use the driver. Do I have to create an iSCSI target first or does the driver do that for me? Does it create a new target for each PV?

[makkes]

I was able to figure it out and the reason is that the driver is trying to connect to port 8080 which isn't opened on my QNAP, only 443 is. This leads to two subsequent problems that I created tickets for: #20, #21.