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.
Maven, docker buildx, jenkins, github actions, helm, ArgoCD, Tekton, Terraform
It's an often-broken Franken-Goldberg machine
I've architected our CI pipeline (newer folks are doing the CD portion), it's a monorepo tamed with CUE and Dagger, runs on Jenkins that needs to simulate an air gapped install of k8s then some helm. Can't imagine using multiple systems for the same piece of the pipeline!
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.