4 ms·
Haven't tried this out but, from the write up, I don't see what the convenience of this is over just using git + {kubectl, kustomize, helm}. The Kubernetes eco
by zomglings 7y ago
Haven't tried this out but, from the write up, I don't see what the convenience of this is over just using git + {kubectl, kustomize, helm}.
The Kubernetes ecosystem is rife with tools like this, and it feels like such a chore to just keep up with every new templating system for YAML files. I have started to just write Go programs that directly talk to the Kubernetes API and manage my rollouts (one step away from operators).
- ff2 7y agoOne key distinction is that this is not yet another templating DSL like Jinja, or Go templates that present an anti-pattern for non-trivial deployments. As an example, take a look at the Grafana Helm chart: https://github.com/bitnami/charts/blob/master/bitnami/grafana/templates/deployment.yaml https://github.com/bitnami/charts/blob/master/bitnami/grafan... It's more curly brackets than YAML :) Instead, kpt's key design philosophy is to keep configuration as data. This makes it easier to develop tooling that operate on configs.