Consider merging helm and argo back ends #182
Description
I feel there is a disconnect between using argoCD and helm. The tool is not really helping you with this but assumes you understand the implications of using one or the other. It also compels you to switch between back ends for some kinds of operation.
One example of this is #181. Most beamlines will be ArgoCD and if you want to debug then you will need kubectl. But kubectl config does not come with the ArgoCD environment.
I would like a world where I don't have to think about the different back ends, I need just one configuration setup and that ec commands I use invoke the necessary tools without me having to think about switching back ends.
I'm not sure exactly what that world looks like and there is the issue of >1 authentication required but I'd like us to have a think about how this could be achieved.
@coretl @marcelldls @GDYendell tagging you for your thoughts on this.