Evaluate migrating to ArgoCD with image updater

[lorenzo-w]

Pros:

• beautiful web ui
• image updater
• larger community

ToDos

• set up both argo-cd and image updater charts
• use existingSecret for oauth2-proxy
• supply adminPassword for erpnext via Helm values
• Replace all Flux HelmReleases with ArgoCD Applications

[lorenzo-w]

⚠️ !!! Problem: ArgoCD does not support Helm lookup!

[lorenzo-w]

Conservative solution: Keep using Flux for deploying third-party apps, only translate this repo's top-level charts to ArgoCD Application CRDs, and outsource any lookups to an extra chart (e.g. managed-secret), which is deployed via Flux.

[lorenzo-w]

Possible other solution: Use Flamingo for an even deeper integration between ArgoCD and Flux, through which you could possibly switch all releases to ArgoCD Apllication CRDs and still use Helm lookup.

[lorenzo-w]

Plan for migrating top-level helm releases from Flux to ArgoCD:

1. Make sure all lookup functionality is outsourced into sub-HelmReleases managed by Flux.
2. Delete the HelmRelease without garbage collection
3. Create a new ArgoCD application from the same top-level chart, which should take ownership of the matching resources seamlessly.

[lorenzo-w]

Question: When deploying Flux HelmReleases with an ArgoCD Application directly, does Argo recognize and display all the sub-resources created by Flux?