3 ms·
"yaml sucks and templated yaml is insane" I'm happy to hear that I'm not the only one that thinks this.
by mring33621 2mo ago
"yaml sucks and templated yaml is insane"
I'm happy to hear that I'm not the only one that thinks this.
- verdverm 2mo agolikewise! 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.
- atkrad 2mo agoYeah, Argo + Helm double templating is rough. I stayed client-side on purpose so you can still inspect the release with normal helm commands.
- verdverm 2mo agoThis is a good bridge to something new eventually. There is Timoni, which was a CUE based attempt to replace Helm, but imo, it stayed too true to helm concepts and missed the opportunities CUE enables. 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.
- mring33621 2mo agoI was recently scolded for telling my coworkers that they are 'nose blind' to the mess that is our CI/CD 'pipeline'. Maven, docker buildx, jenkins, github actions, helm, ArgoCD, Tekton, Terraform It's an often-broken Franken-Goldberg machine
- verdverm 2mo agooooh that smell, can't you smell that smell? 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!
- atkrad 2mo agoSame. Templated YAML is what pushed me away from writing charts by hand.