[
https://issues.apache.org/jira/browse/FLINK-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24624:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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
> Assignee: Aitozi
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> 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.20.1#820001)
