gyfora commented on PR #195: URL: https://github.com/apache/flink-kubernetes-operator/pull/195#issuecomment-1118364736
@tweise After discussing this in detail with @morhidi we came to the following conclusions: If there is a CR incompatibility issue, the operator won't be able to reconcile it anyways so the recovery logic (or anything else in the controller) won't take effect so the user can simply delete the jobmanager deployment. Otherwise if the user wants to stop the job they simply need to suspend the FlinkDeployment. The operator should do anything in it's power to make sure that the Flink/Cluster state reflects what's in the FlinkDeployment, therefore automatic jm deployment recovery should be the default in 1.15 and later. -- 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]
