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

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-15816:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating the community on your progress.  If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it.


> Limit the maximum length of the value of kubernetes.cluster-id configuration option
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-15816
>                 URL: https://issues.apache.org/jira/browse/FLINK-15816
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.10.0, 1.14.1
>            Reporter: Canbin Zheng
>            Assignee: Alexander Preuss
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>             Fix For: 1.11.0
>
>         Attachments: image-2020-01-31-20-54-33-340.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)