You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2021/11/03 09:48:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17437864#comment-17437864 ]
Yang Wang commented on FLINK-24631:
-----------------------------------
I think it makes sense to use minimal selectors to filter JobManager and services. I have assigned this ticket to you. Go ahead.
> 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)