search

wave-k8s / wave

Kubernetes configuration tracking controller
Apache License 2.0
647 stars 82 forks source link

kustomize vs wave? #53

Closed afirth closed 3 years ago

afirth commented 5 years ago

Saw your lightning talk, wondering what this does compared to kustomize's generator functionality? Thanks for speaking!

KlavsKlavsen commented 4 years ago

kustomize does not seem to have a way to handle redeploying on secrets changes? I haven't seen how kustomize's configmapGenerator works - it may perform better than this projects approach? I'm just browsing - and trying to see what way to myself :)

wonderhoss commented 3 years ago

The purpose of Wave is to ensure Pods consuming a ConfigMap always run with the current version of that config, regardless of how or why they changed, even at runtime (e.g. by another process). The ConfigMapGenerator in kustomize runs as part of a kustomization, i.e. at deploy-time (or earlier).

If your deployment flow ensures that each time a ConfigMap is updated all consuming software is also updated, then you may not need Wave at all.