[
https://issues.apache.org/jira/browse/FLINK-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150884#comment-17150884
]
Chesnay Schepler commented on FLINK-17032:
------------------------------------------
I think this goes in a better direction [~felixzheng].
> _The reason why the name of the job manager pods does not contain a resource
> type is that: when we create a Deployment, it creates a {{replicaset}} and
> add a random string{{(*66cf4d99b5)* }}to the deployment name for the
> {{replicaset}} name. The {{replicaset}} creates the pod(s). Replica set also
> adds another random string to each {{pod}}._
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?
Could we still not include "JobManager" in the pod/replicaset name?
> _Given that the job manager pods do not contain a resource type in their
> names, we don't specify a resource type for the task manager pods as well._
That sounds reasonable.
> 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)
