[
https://issues.apache.org/jira/browse/FLINK-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239009#comment-17239009
]
Yang Wang commented on FLINK-20359:
-----------------------------------
If you could, I prefer to spin off the implementation of this ticket from
[PR-14005| [https://github.com/apache/flink/pull/14005].] Then it will be
easier to review. Also could you refine the commit message based on our
contribution guide[1]?
[1].
https://flink.apache.org/contributing/code-style-and-quality-pull-requests.html#commit-naming-conventions
> 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
> Priority: Major
> Fix For: 1.12.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)
