Earlier quoted context omitted.
likewise! I cannot understand the field of devops willingness not only to endure this, but find double templated yaml (Argo+helm) appealing. So many of my peers prefer to do what everyone else is doing and slog through the pain.
Yeah, Argo + Helm double templating is rough. I stayed client-side on purpose so you can still inspect the release with normal helm commands.
From experience, you will likely get the most pushback / dropoff from the DSL. Like people want to get at helm if needed, creating an abstraction (DSL) of the underlying k8s constructs will make it too challenging to get at the actual underlying k8s resources. I get that yaml is repeatative and there is a place for reuse, but a custom CLI and DSL is not paletable.