Re:Tanka: Our way of deploying to Kubernetes
by cbushko on Monday January 13, 2020 @04:28PM
(#22038835)
I do find that state management is a bit of a pain which is why I have the layered approach listed above. By keeping components/modules separate I am able to update things without worrying about breaking others. Each namespace has it's own state while the kube cluster has it's own state too.
I find state to be invaluable when a deploy of anything fails.
I find state to be invaluable when a deploy of anything fails.