gyfora commented on PR #195: URL: https://github.com/apache/flink-kubernetes-operator/pull/195#issuecomment-1117600634
@tweise hm, thats a good question. In general my logic for making the default behaviour to recover (at least from Flink 1.15 onward), is this is how operators usually work. If you delete a resource managed by an operator it is usually brought back up for you. I would consider the jobmanager deployment a managed resource so we should try to do everything to recover if possible. The only reason I made this default off in Flink 1.14 is because we cannot keep the clusters around after the job terminated which produces a bunch of annoying cases for failed/finished jobs. As for what to do if your FlinkDeployment CR gets stuck and you cannot remove it, I don't really know :/ We should make sure that we do not introduce breaking changes 😄 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
