【Feature】flink on k8s session trying to stop cluster exception

[kuihz]

Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

Local idea debugging, after starting a cluster in k8s session mode, and then operating to stop the cluster, the pod has been stopped, but the cluster status in the database is not synchronized, because I hit a breakpoint at the stop cluster code, and this cluster cannot be stopped, only the database can be modified, i hope to add a real-time synchronization of the status to the cluster status in the feature

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wolfboys]

Thanks for your feedback. We are closing this issue because it is outdated.