<p>Are there any problems when using helm 2 and helm 3 in parallel - on the same cluster?</p>

<p>Reason behind is, that the Terraform helm provider is still NOT available for helm 3. But with another application we'd like to proceed with helm 3.</p>

<p>Have you maybe tried this? Or did you run into some problems?</p>

<p>Helm 2 and Helm 3 can be installed concurrently to manage the same cluster. This works when Helm 2 uses ConfigMaps for storage as Helm 3 uses Secrets for storage. There is however a conflict when Helm 2 uses Secrets for storage and stores the release in the same namespace as the release. The conflict occurs because Helm 3 uses different tags and ownership for the secret objects that Helm 2 does. It can therefore try to create a release that it thinks does not exist but will fail then because Helm 2 already has a secret with that name in that namespace. </p>

<p>Additionally, Helm 2 can be migrated to enable Helm 3 to manage releases previously handled by Helm 2 ref. <a href="https://github.com/helm/helm-2to3" rel="nofollow noreferrer">https://github.com/helm/helm-2to3</a>. This also works when Helm 2 uses ConfigMaps for storage as Helm 3 uses Secrets for storage. There is a conflict again however when using secrets because of the same naming convention. 
A possible solution around this would be for Helm 3 to use a different naming convention for release versions.</p>
