You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/03/30 11:27:00 UTC

[jira] [Closed] (FLINK-31592) Configurable deletion propagation for Flink resources

     [ https://issues.apache.org/jira/browse/FLINK-31592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-31592.
------------------------------
    Fix Version/s: kubernetes-operator-1.5.0
       Resolution: Fixed

merged to main 6620466d31df7b22e4cae4ed0bd2eab70280c8c8

> Configurable deletion propagation for Flink resources
> -----------------------------------------------------
>
>                 Key: FLINK-31592
>                 URL: https://issues.apache.org/jira/browse/FLINK-31592
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.5.0
>
>
> Currently we use the default (background) deletion propagation when we delete Kubernetes resources such as the JobManager deployment.
> In most cases this is acceptable however this can lead to lingering resources when the garbage collection is slow on the k8s cluster. We therefore propose to make this configurable and also change the default to Foreground which is more predictable and works better for our purposes in the operator.



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