4 ms·
Having to do conditional logic in it, like: matchExpressions: - key: app operator: In values: - myservice Rather than, if (app=="myservice")
by billfor 6y ago
Having to do conditional logic in it, like:
matchExpressions:
- key: app
operator: In
values:
- myservice
Rather than, if (app=="myservice")
- jonfw 6y agoWhy would you do this in a Kubernetes context?
- billfor 6y agoTo specify a podAffinityTerm, amongst others.
- blandflakes 6y agoYour position here seems to be that YAML is a reasonable configuration language. It kinda is. But that's not how it's used in Kubernetes. It's used as a declarative DSL that you use to specify your deployments, and it is HORRIFIC. Extremely nested things where the equivalent actual code to do that would be shorter. Things that are inexpressible. Backwards-incompatible changes to your YAML that actually make it impossible to deploy changes that bring your YAML up to spec if your cluster's master node upgraded first. YAML gives nothing here. jsonnet really isn't a drastic improvement, IMO, except that it lets you express some repetitive parts without having to figure out how many times a template engine is going to indent your YAML.