[ https://issues.apache.org/jira/browse/FLINK-24631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aitozi updated FLINK-24631: --------------------------- Description: We create deployment use the pod selector directly from labels, which is not necessary and may cause problem when some user label value have changed (may be by third-party system). This may lead to dangling pod or service can not select pods. I suggest to use minimal and stable flink internal selectors to select the JobManager pod like {{app=xxx, component=jobmanager}} and service, taskmanager pod and so on. was: We create deployment use the pod selector directly from labels, which is not necessary and may cause problem when some user label value have changed (may be by third-party system). This may lead to dangling pod or service can not select pods. I think it's better to use minimal and stable selector to select the JobManager pod like {{app=xxx, component=jobmanager}} and service, taskmanager pod and so on. > Avoiding directly use the labels as selector for deployment and service > ----------------------------------------------------------------------- > > Key: FLINK-24631 > URL: https://issues.apache.org/jira/browse/FLINK-24631 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes > Affects Versions: 1.14.0 > Reporter: Aitozi > Priority: Major > > We create deployment use the pod selector directly from labels, which is not > necessary and may cause problem when some user label value have changed (may > be by third-party system). This may lead to dangling pod or service can not > select pods. > I suggest to use minimal and stable flink internal selectors to select the > JobManager pod like {{app=xxx, component=jobmanager}} and service, > taskmanager pod and so on. -- This message was sent by Atlassian Jira (v8.3.4#803005)