Update Helm Chart to add more flexibility

[manfuin]

When deploying for my use-case I have refactored couple of places in the chart:

• OAUTH machinery in explicitly enabled/disabled instead of relying on interlink usage of the socket. It might be IP connectivity without OAUTH but NetworkPolicies or even ServiceMesh instead.
• DataRootFolder is not just static path but a volume mount definition instead. This offers a flexibility to define whatever volume your infra is required to get it working: hostPath, nfs, PVC, etc.
• Plugin container fixes (main one: mount plugin config instead of interlink config)
• More conditionals to avoid mounting unnecessary volumes or defining unnecessary environment if feature is disabled

Hope you can find it useful.

P.S. I didn't bump the chart version in PR.

[dciangot]

@manfuin thanks for this PR, I agree with your points.

Can you tell which scenario did you test? So I can give a quick spin to the others and checking that they still working?

[dciangot]

ok, If I recall it correctly should be the edge case the one you tested.

Let me try the in-cluster and tunneled oene. If everything still works I'll merge the PR

[dciangot]

LGTM. sorry for the delay @manfuin , I rechecked all the current deployment I could replicate, and looks like good go.

[manfuin]

Thanks @dciangot! Sorry I had overlooked all previous github emails in my mailbox. It was actually both in-cluster and edge I was playing with.