[ https://issues.apache.org/jira/browse/FLINK-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433449#comment-17433449 ]
Aitozi commented on FLINK-24624: -------------------------------- So the {{client.stopAndCleanupCluster(clusterId)}} should cover the whole block of {{deploySessionCluster}}. Besides, I think it may be more user-friendly to expose all the required permission to user in-advance. I follow the [Native Kubernetes |https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/native_kubernetes/#session-mode] doc, but still get some error about permission. May be we could add an option {{kubernetesSessionCli}} to print all the permissions should apply before starting a cluster. I create a [ticket|https://issues.apache.org/jira/browse/FLINK-24625] for this. Looking forward to your idea on this cc [~wangyang0918] [~trohrmann] > Add clean up phase when kubernetes session start failed > ------------------------------------------------------- > > Key: FLINK-24624 > URL: https://issues.apache.org/jira/browse/FLINK-24624 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes > Affects Versions: 1.14.0 > Reporter: Aitozi > Priority: Major > > Serval k8s resources are created when deploy the kubernetes session. But the > resource are left there when deploy failed. This will lead to the next > failure or resource leak. So I think we should add the clean up phase when > start failed -- This message was sent by Atlassian Jira (v8.3.4#803005)