3 ms·
Original creator of both of those here. I recommend just generating things out straight with the `jsonnet -m` command, and then doing `kubectl diff` on a PR and
by brancz 4y ago
Original creator of both of those here. I recommend just generating things out straight with the `jsonnet -m` command, and then doing `kubectl diff` on a PR and apply on merge. Scaled huge amount of infra this way and it’s easily understandable and extensible.
To clean up the diff a bit I recommend using: https://github.com/sh0rez/kubectl-neat-diff https://github.com/sh0rez/kubectl-neat-diff
Hope it’s helpful!
- bdsa 4y agoI have to admit I'm a little starstruck to see your username replying to me. Thanks for all the effort and expertise you bring to bear on observability! We're using exactly that diff-on-PR/apply-on-merge approach, checking the generated manifests in for easier reviews, but I found just using jsonnet -m made it difficult to DRY things out (e.g. set some URL values differently per environment) so I'd be curious to hear how you approach that? Would you wrap the customised kube-thanos/prometheus-operator "calls" in another library?