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

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2022/05/09 06:57:00 UTC

[jira] [Commented] (FLINK-26812) Flink native k8s integration should support owner reference

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

Robert Metzger commented on FLINK-26812:
----------------------------------------

This is a related discussion: https://issues.apache.org/jira/browse/FLINK-22262?focusedCommentId=17408210&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17408210

> Flink native k8s integration should support owner reference
> -----------------------------------------------------------
>
>                 Key: FLINK-26812
>                 URL: https://issues.apache.org/jira/browse/FLINK-26812
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.14.4
>            Reporter: Thomas Weise
>            Priority: Major
>
> Currently the JobManager deployment and other resource created by the integration do not support the owner reference, allowing for the possibility of them to become orphaned when managed by a higher level entity like the CR of the k8s operator. Any top level resource created should optionally have an owner reference to ensure safe cleanup when managing entity gets removed.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)