[
https://issues.apache.org/jira/browse/FLINK-26812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510969#comment-17510969
]
Yang Wang commented on FLINK-26812:
-----------------------------------
I am not sure which orphaned resources you are talking about. IIRC, the
TaskManager pods, JobManager service, flink configmap should already set the
owner reference to the JobManager deployment.
As for the HA ConfigMaps, it is by-design not to set the owner reference to
avoid resource leak in the DFS(e.g. S3, HDFS).
[1].
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/overview/#high-availability-data-lifecycle
[2].
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/#high-availability-data-clean-up
> 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.1#820001)
