Uuuuh not using YAML. Controversial.
(in the docker/k8s ecosphere, where YAML seems ubiquitous)
I don't love YAML though I am not sure Starlark looks any more readable.
YACL => Yet another config language...?
I don't love YAML though I am not sure Starlark looks any more readable.
YACL => Yet another config language...?
The most sensible approach I've seen is to use jsonnet+kubecfg. This lets me use a somewhat sane, composable, turing complete language that spits out a tree of k8s objects. I can use as much or little repeated definitions (or abstractions) as I like. Then kubecfg performs all the kubectl invocations to actually make the cluster state match my calculated definitions.
I keep seeing helm, and the overall idea of a "package manager" sounds nice, but having looked at some charts, and tried to understand the value proposition, I get a very uneasy feeling somehow. Perhaps it's lack of familiarity? but your comment seems to suggest something is inherently wrong, so I'd love to understand more...