[
https://issues.apache.org/jira/browse/FLINK-24631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Wang closed FLINK-24631.
-----------------------------
Resolution: Fixed
Fixed via:
master: e192243abb55df7b2c6df39d137fa29d6ec66d11
1.14: 9d114b08b78d74c4d9a198c09bd8ad7c99eeaf0e
1.13: b9c729eef92c051ae96a99810882e4500201164f
> 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, 1.13.3
> Reporter: Aitozi
> Assignee: Aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0, 1.14.1, 1.13.4
>
>
> 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.20.1#820001)
