[jira] [Created] (FLINK-17032) Naming convention unification for all the Kubernetes Resources

[Shang Yuanchun (Jira)]

Canbin Zheng created FLINK-17032:
------------------------------------

             Summary: 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
             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}-inter-svc
 * The external Service: ${clusterId}-rest-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)