Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-15788 Various Kubernetes integration improvements
  3. FLINK-15816

Limit the maximum length of the value of kubernetes.cluster-id configuration option

    XMLWordPrintableJSON

    Details

      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.

        Attachments

        1. image-2020-01-31-20-54-33-340.png
          313 kB
          Canbin Zheng

          Issue Links

            Activity

              People

              • Assignee:
                felixzheng Canbin Zheng
                Reporter:
                felixzheng Canbin Zheng
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m