You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/03/01 08:23:00 UTC

[jira] [Closed] (FLINK-26336) Deletion should remove HA related configmaps also

     [ https://issues.apache.org/jira/browse/FLINK-26336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-26336.
------------------------------
    Resolution: Fixed

Merged: 38c366de0d8fa11751051eadbddcf19cb1f31e8f

> Deletion should remove HA related configmaps also
> -------------------------------------------------
>
>                 Key: FLINK-26336
>                 URL: https://issues.apache.org/jira/browse/FLINK-26336
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Critical
>              Labels: pull-request-available
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)