Ask HN: How do you handle Kubernetes manifest source control?
How do you handle maintaining manifests for Kubernetes clusters when you have multiple clusters running slightly tweaked variations of each manifest?
(and FWIW - currently my approach is to require that each environment is config-identical, allowing simple source control to provide the solution - but I appreciate that's probably a property that's very hard to maintain in many environments)