Need to investigate the possibilities of how we can deploy VolSync on  non-OpenShift managed clusters via the existing volsync-addon-controller

• Deployments could be done via appsub - but this will be deprecated, also requires creasting channel resources on the hub.  Some investigation has been done already doing this, it is possible but requires managed clusters also to have access directly to the helm repo.
• Deployments could be done via argo CD deployments - this for the moment is ruled out due to argo CD not always being present on managed clusters, and particularly on non-OpenShift mangaed clusters.
• Deployments using helm charts that are rendered by the volsync-addon-controller
  • Investigation so far:
    • Helm charts can be rendered using helm apis and then put into the manifestwork generated by the volsync-addon-controller (similar to what an addon using the addon-framework in helm mode would do).
    • We can package helm charts into the volsync-addon-controller but this requires that we package specific version or versions with ACM versions
    • We can also have the helm charts pulled down from a repo prior to rendering.  Current thinking is we will have a combination of this (as optional for the user) and packaging a specific version locally.