Deployment Configs do not allow batch behavior, but they do allow “test” behavior that allows you to trigger a scale up when a change happens, and if everything succeeds you’ll get a “passing” deployment. When success or failure happens it is scaled down to zero. This can be used to validate that things deploy correctly.
But if you are doing actual batch workloads, jobs would be more appropriate.
On Nov 12, 2018, at 9:01 AM, François VILLAIN <f villain linkbynet com> wrote: