YAML is okay for representing a simple declarative configuration. It starts to break down when you try to encode too much operational logic into it. If we step

YAML is okay for representing a simple declarative configuration. It starts to break down when you try to encode too much operational logic into it. If we step back, there are a few different strategies for dealing with operational logic. From least scalable to most (roughly): 1. Human processes (ex: checklist) 2. In the config itself (ex: Kubernetes' YAML) 3. A config generator (ex: Helm, Kustomize) 4. Software (ex: Kubernetes Operator) I see a lot of people get stuck doing one for too long. When doing one becomes unwieldy, it's time to consider the next. That or find a way to reduce the need for all that operational logic.