So in 1.2, Deployment API facilitates the transition from state to state for an RC or a pod. This provides a basic form of revision history, but isn't "versioni

So in 1.2, Deployment API facilitates the transition from state to state for an RC or a pod. This provides a basic form of revision history, but isn't "versioning" - it's more if you could only go back one step. For us, we see the big use case for full deployment versioning when there are multiple kube objects and config files to track. Already this is introducing some complication into developer workflows - ex: I have a bunch of services, rc's, and secrets. They are parameterized by this configuration. Now I've updated the configuration. I want to propagate that configuration to my cluster "with no downtime” - right now there isn't an easy way to do this.