If you run `kubectl describe pod ...` on the affected pod, you should see a reason why the previous pod has terminated (eg. OOM killed by Kubernetes).
Best, D. On Thu, Jul 22, 2021 at 9:30 AM Fabian Paul <fabianp...@ververica.com> wrote: > CC user ML > >
