You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2021/10/25 10:53:00 UTC
[jira] [Updated] (FLINK-24631) Avoiding directly use the labels as
selector for deployment and service
[ 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) .
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.
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 changed by other system).
I think it's better to use the 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) .
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)