Thanks! I had briefly used kustomize in the past, and it looks really useful for creating alternative dev/staging/production environments from a common base.
In the end I decided that I'd collapse all environments down to behave identically, which is simpler, but does add a few constraints for development in particular.
Will take another browse through while considering options for upcoming infrastructure :)
The problem for us monitoring / observability people with kustomize is its limitation to be purely templating for Kubernetes. However we also want to template a lot of things like for example Prometheus configuration. Jsonnet can bridge that gap between the two worlds and in the end generate a ConfigMap YAML file that includes another YAML file Prometheus, as an example.
I tried to use kustomize recently but could not figure out how to write Job/CronJob properly. I wanted to use the configGenerator/secretGenerator, with prod/stage/dev.
jka|6 years ago
In the end I decided that I'd collapse all environments down to behave identically, which is simpler, but does add a few constraints for development in particular.
Will take another browse through while considering options for upcoming infrastructure :)
MetalMatze|6 years ago
slig|6 years ago