Hi, We are currently using Flink 1.6 standalone mode, but the lack of isolation is a headache for us. At present, I am trying application mode of Flink 1.13.0 on native K8s.
I found that as soon as the job ends, whether it ends normally or abnormally, the jobmanager can no longer be accessed, so the "flink list" command cannot get the final state of the job. K8s pod will also be deleted immediately, "kubectl get pod" can only see "running", "terminating", and then "not found". The Flink job needs to be managed by our internal scheduling system, so I need to find a way to let the scheduling system know whether the job ends normally or abnormally. Is there any way?
