[BUG] Double resources with HelmReleases

[christianh814]

When you migrate over a HelmRelease, it will "double" everything. Example using podinfo helmchart after migration

$ Kubectl get all -n podinfo-system
NAME                                          READY   STATUS    RESTARTS   AGE
pod/podinfo-758bbb57d6-c8pzv                  1/1     Running   0          14m
pod/podinfo-758bbb57d6-crqt4                  1/1     Running   0          14m
pod/podinfo-system-podinfo-55879b6fd8-qx8xt   1/1     Running   0          15m
pod/podinfo-system-podinfo-55879b6fd8-s4tmn   1/1     Running   0          15m

NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/podinfo                  ClusterIP   10.96.189.154   <none>        9898/TCP,9999/TCP   14m
service/podinfo-system-podinfo   ClusterIP   10.96.190.92    <none>        9898/TCP,9999/TCP   15m

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/podinfo                  2/2     2            2           14m
deployment.apps/podinfo-system-podinfo   2/2     2            2           15m

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/podinfo-758bbb57d6                  2         2         2       14m
replicaset.apps/podinfo-system-podinfo-55879b6fd8   2         2         2       15m

Notice how there is podinfo- and podinfo-system-podinfo-. A workaround (potentially dangerous) is to delete the resources by hand and sync the application.

This worked on my test system:

$ kubectl delete all --all -n podinfo-system && argocd app sync podinfo

$ kubectl get all -n podinfo-system
NAME                           READY   STATUS    RESTARTS   AGE
pod/podinfo-758bbb57d6-dlclg   1/1     Running   0          15s
pod/podinfo-758bbb57d6-l4bjr   1/1     Running   0          15s

NAME              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/podinfo   ClusterIP   10.96.170.133   <none>        9898/TCP,9999/TCP   20s

NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/podinfo   2/2     2            2           15s

NAME                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/podinfo-758bbb57d6   2         2         2       15s

mta should account for this somehow.

[christianh814]

Should be fixed by 40ff6a6

Keeping this open until the next release.