I've been reading Octopus Deploy's article about ArgoCD anti-patterns, and I came across anti-pattern #17: Hardcoding Helm data inside Argo CD applications:
( https://octopus.com/blog/30-argo-cd-antipatterns-for-gitops#anti-pattern-17--hardcoding-helm-data-inside-argo-cd-applications )
The general idea is separation of concerns. You shouldn't be mixing information that operators/administrators are concerned about (ArgoCD App CRD) with information that developers are concerned about (Helm values). And there were a bunch of other things under that anti-pattern that were mentioned.
Now, I no longer use ArgoCD since I moved to FluxCD + Flux Operator. However, I'm wondering if the same "principle" applies to HelmRelease in FluxCD. When I examine the HelmRelease CRD, it's doing a lot of things that are very close to how you'd normally use "helm install".…