You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2021/02/02 01:38:00 UTC
[jira] [Closed] (FLINK-20359) Support adding Owner Reference to Job
Manager in native kubernetes setup
[ https://issues.apache.org/jira/browse/FLINK-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xintong Song closed FLINK-20359.
--------------------------------
Resolution: Fixed
Merged via
* master (1.13): 06d94bf2fbb9a920997d88bd44a4b8be36e1078d
* release-1.12: dc812271102c08c05d966e4c43cb2c1b1c0a03f2
> Support adding Owner Reference to Job Manager in native kubernetes setup
> ------------------------------------------------------------------------
>
> Key: FLINK-20359
> URL: https://issues.apache.org/jira/browse/FLINK-20359
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
> Affects Versions: 1.11.2
> Reporter: Boris Lublinsky
> Assignee: Boris Lublinsky
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.2, 1.13.0
>
>
> Flink implementation is often a part of the larger application. As a result a synchronized management - clean up of Flink resources, when a main application is deleted is important. In Kubernetes, a common approach for such clean up is usage of the owner's reference ([https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/)]
> Adding owner reference support to Flink Job manager would be a nice addition to Flink kubernetes native support to accommodate such use casesĀ
--
This message was sent by Atlassian Jira
(v8.3.4#803005)