[jira] [Commented] (FLINK-30036) Force delete pod when k8s node is not ready

["Yang Wang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-30036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634766#comment-17634766 ] 

Yang Wang commented on FLINK-30036:
-----------------------------------

I prefer to believe the terminating pod should not be counted into the quota. Given that when the node turns to ready state, the terminating pod will be cleaned up automatically. I lean towards not to introduce such magic logic in the {{{}FlinkKubeClient#stopPod{}}}.

> Force delete pod when  k8s node is not ready
> --------------------------------------------
>
>                 Key: FLINK-30036
>                 URL: https://issues.apache.org/jira/browse/FLINK-30036
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Peng Yuan
>            Priority: Major
>              Labels: pull-request-available
>
> When the K8s node is in the NotReady state, the taskmanager pod scheduled on it is always in the terminating state. When the flink cluster has a strict quota, the terminating pod will hold the resources all the time. As a result, the new taskmanager pod cannot apply for resources and cannot be started.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)