2 ms·
I'm not saying there isn't a use case for this, it's just that for the most part I prefer dumping what I have from an immutable git commit into the Kube API. If
by cfors 7y ago
I'm not saying there isn't a use case for this, it's just that for the most part I prefer dumping what I have from an immutable git commit into the Kube API. If something needs to happen after the fact for governance or injecting sidecars, so be it but that is out of the scope of what I am deploying.
- bacongobbler 7y agoThen that's fine. If no updates were made to the resource since the last update, then the patch will not look at the live state. I highly suggest re-reading the FAQ front-to-back on this subject. I spent a lot of time explaining the details on this subject. If you have any questions/concerns, we are always happy to discuss further on github. https://helm.sh/docs/faq/#improved-upgrade-strategy-3-way-strategic-merge-patches https://helm.sh/docs/faq/#improved-upgrade-strategy-3-way-st...
- mfer 7y agoTo take a step back... we're discussing a personal opinion on how to manage things compared to what k8s has documented and what's happening with other tools like service meshes. I respect what someone has as an opinion. I just would like others to know where the opinion differs from the docs and tools out there. People can make their own choices.