You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fred k (Jira)" <ji...@apache.org> on 2022/06/16 03:45:00 UTC

[jira] [Updated] (FLINK-28087) FlinkDeployment meta.name validation

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

Fred k updated FLINK-28087:
---------------------------
    Summary: FlinkDeployment meta.name validation  (was: FlinkDeployment name validation)

> FlinkDeployment meta.name validation
> ------------------------------------
>
>                 Key: FLINK-28087
>                 URL: https://issues.apache.org/jira/browse/FLINK-28087
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Fred k
>            Priority: Major
>             Fix For: kubernetes-operator-1.1.0
>
>         Attachments: operator-flink.jpg
>
>
> The FlinkDeployment CR meta.name must be match the regex:
> {code:java}
>  '[a-z]([-a-z0-9]*[a-z0-9])?'{code}
> By RRC-1035, a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?').
> The rest service name of Flink Cluster uses the meta.name of FlinkDeployment, So meta.name value must follow the convention of DNS-1035 label.
> To avoid operator repeatedly creating and destroying flink clusters due to invalid service name, So I suggest add validation for meta.name of FlinkDeployment CR.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)