Subject: Running JobManager as Deployment instead of Job

In one case however, we do want to retain the same cluster id ( think
ingress on k8s  and thus SLAs with external touch points ) but it is
essentially a new job ( added an incompatible change but at the interface
level it retains the same contract ) , the only way seems to be to remove
the chroot/subcontext from ZK , and relaunch , essentially deleting ant
vestiges of the previous incarnation. And that is fine if that is indeed
the process.
On Fri, Feb 8, 2019 at 7:58 AM Till Rohrmann <[EMAIL PROTECTED]> wrote: