[
https://issues.apache.org/jira/browse/FLINK-27273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552247#comment-17552247
]
Gyula Fora commented on FLINK-27273:
------------------------------------
I guess we could do a best effort support for ZK using the utilities you
mentioned. But we have to make sure that those utils are compatible across
flink versions.
For Kubernetes HA it is probably still better to delete the configmaps by label.
cc [~mbalassi] [~morhidi]
> Support both configMap and zookeeper based HA data clean up
> -----------------------------------------------------------
>
> Key: FLINK-27273
> URL: https://issues.apache.org/jira/browse/FLINK-27273
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Aitozi
> Priority: Major
> Fix For: kubernetes-operator-1.1.0
>
>
> As discussed in
> [comments|https://github.com/apache/flink-kubernetes-operator/pull/28#discussion_r815695041]
> We only support clean up the ha data based configMap. Considering that
> zookeeper is still widely used as ha service when deploy on the kubernetes, I
> think we should still take it into account, otherwise, It will come up with
> some unexpected behavior when play with zk ha jobs. For example, it will
> recover old JobGraph when redeploy the application.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
