[FLINK-15816] Limit the maximum length of the value of kubernetes.cluster-id configuration option

• Type: Sub-task
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.10.0, 1.14.1
• Fix Version/s: 1.11.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available stale-assigned
• Assignee: Alexander Preuss
• Reporter: Canbin Zheng
• Created: 31/Jan/20 01:50
• Updated: 17/Mar/22 10:44

Description

Two Kubernetes Service will be created when a session cluster is deployed, one is the internal Service and the other is the rest Service, we set the internal Service name to the value of the kubernetes.cluster-id configuration option and then set the rest Service name to  ${kubernetes.cluster-id} with a suffix -rest appended, said if we set the kubernetes.cluster-id to session-test, then the internal Service name will be session-test and the rest Service name be session-test-rest; there is a constraint in Kubernetes that the Service name must be no more than 63 characters, for the current naming convention it leads to that the value of kubernetes.cluster-id should not be more than 58 characters, otherwise there are scenarios that the internal Service is created successfully then comes up with a ClusterDeploymentException when trying to create the rest Service.

Issue Links

• relates to: FLINK-25393 Make ConfigMap Name for Leader Election Configurable
• links to: GitHub Pull Request #11708
• links to: GitHub Pull Request #17819
• links to: GitHub Pull Request #17827
• links to: GitHub Pull Request #17828