[
https://issues.apache.org/jira/browse/FLINK-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151246#comment-17151246
]
Canbin Zheng commented on FLINK-17032:
--------------------------------------
> _Not sure I quite understand this; is it that the JobManager pods inherits
> the replicaset name + a random suffix, and thus having a resource type "pod"
> doesn't make sense since it applies to both the pods and replicaset?_
_Why does the replicaset need a random string? Doesn't the clusterId prevent
clashes? Or can there be multiple replicasets with the same clusterId?_
If one uses K8s Deployments, then the naming convention by design in Kubernetes
is as follows:
|--- Deployment: < name >
│{{-----}}└─ Replica Set: < name >-< rs >
│{{--------}}└─ Pod: < name >-< rs>-< RandomString >
Refer to [https://github.com/kubernetes/kubernetes/issues/75557]
> _Could we still not include "JobManager" in the pod/replicaset name?_
I think yes.
> Naming convention unification for all the Kubernetes Resources
> --------------------------------------------------------------
>
> Key: FLINK-17032
> URL: https://issues.apache.org/jira/browse/FLINK-17032
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Canbin Zheng
> Priority: Minor
> Fix For: 1.11.0
>
>
> Currently, the naming rules are different among the Kubernetes resources we
> have created, the rules are as follows:
> # The Deployment: ${clusterId}
> # The internal Service: ${clusterId}
> # The external Service: ${clusterId}-rest
> # The Flink Configuration ConfigMap: flink-config-${clusterId}
> # The Hadoop Configuration ConfigMap: hadoop-config-${clusterId}
> # The JobManager Pod: ${clusterId}\-${random string}-${random string}
> # The TaskManager Pod:
> ${clusterId}\-taskmanager-${currentMaxAttemptId}-${currentMaxPodId}
> In the future, we would add other Kubernetes resources, and it would be
> better to have a unified naming convention for all of them.
> This ticket proposes the following naming convention:
> * The Deployment: ${clusterId}
> * The internal Service: ${clusterId}-internal-svc
> * The external Service: ${clusterId}-external-svc
> * The Flink Configuration ConfigMap: ${clusterId}-flink-config
> * The Hadoop Configuration ConfigMap: ${clusterId}-hadoop-config
> * The JobManager Pod: ${clusterId}\-${random string}-${random string}
> * The TaskManager Pod:
> ${clusterId}\-taskmanager-${currentMaxAttemptId}-${currentMaxPodId}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
