Is there any way so that the `FlinkDeployment` (`f...
# random
h
Is there any way so that the
FlinkDeployment
(
flink-kubernetes-operator
) does not launch the job in a detached way?, I need to get some metrics when the job is finished, things like checking the number of records migrated
g
There is no possibility for attached execution.
That would basically mean we wait / execute user code inside the operator which is not part of the current model and would make the architecture fragile in large clusters
1
👍 1