[FLINK-35123] Flink Kubernetes Operator should not do deleteHAData

• Type: Technical Debt
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: kubernetes-operator-1.7.0, kubernetes-operator-1.8.0
• Component/s: Kubernetes Operator
• Assignee: Unassigned
• Reporter: Fei Feng
• Created: 16/Apr/24 08:18
• Updated: 16/Apr/24 08:54

Description

we use flink HA based on zookeeper. when a lots of FlinkDeployment was deleting, operator will be spend to many time in cleanHaData. the jstack show that reconcile thread was hang on disconnect with zookeeper. this made deleting flinkdeployment was slowly. 

 

I don't understand why flink kubernetes operator need cleanHAdata , as aitozi comment in PR  FLINK-26336 Call cancel on deletion & clean up configmaps as well #28

it's a bit of out of scope of the operator responsibility or ability

and I'm totally agree with his point. 

and I want to know why we call don't call RestClusterClient#shutDownCluster interface, which is

1. more graceful and reasonable (operator need not care whether flink app enable ha or not) 2. compatible across flink versions .   

 

 

Issue Links

• is related to: FLINK-27273 Support both configMap and zookeeper based HA data clean up