Details
-
Sub-task
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
Description
At the moment the deletion logic simply deletes the Flink job deployment.
As wangyang0918 correctly pointed out in another ticket, deployment deletion does not remove HA related configmaps (this is intentional from Flink side)
This means if the user were to resubmit a new FlinkDeployment under the same name, the job would pick up the HA state and the last checkpoint from the delete resource. This is probably unexpected and we should delete the configmaps after deleting the deployment.