[
https://issues.apache.org/jira/browse/FLINK-28087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred k updated FLINK-28087:
---------------------------
Description:
The name of FlinkDeployment CR meta.name must be match the regex:
{code:java}
'[a-z]([-a-z0-9]{0,43}[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|https://github.com/apache/flink-kubernetes-operator/pull/%5B-a-z0-9%5D*%5Ba-z0-9%5D]?').
The rest service name of Flink Cluster uses the meta.name of FlinkDeployment
CR, So the value of meta.name must follow the convention of DNS-1035 label.
The length of the value of name must be no more than 45 characters. See [Limit
the value of kubernetes.cluster-id to have no more than 45 characters
|https://github.com/apache/flink/pull/11708]
To avoid operator repeatedly creating and destroying flink clusters due to
invalid service name, So I suggest add validation for the name of
FlinkDeployment CR.
was:
The meta.name of FlinkDeployment CR meta.name must be match the regex:
{code:java}
'[a-z]([-a-z0-9]{0,43}[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|https://github.com/apache/flink-kubernetes-operator/pull/%5B-a-z0-9%5D*%5Ba-z0-9%5D]?').
The rest service name of Flink Cluster uses the meta.name of FlinkDeployment
CR, So the value of meta.name must follow the convention of DNS-1035 label.
The length of meta.name value must be no more than 45 characters. See [Limit
the value of kubernetes.cluster-id to have no more than 45 characters
|https://github.com/apache/flink/pull/11708]
To avoid operator repeatedly creating and destroying flink clusters due to
invalid service name, So I suggest add validation for the meta.name of
FlinkDeployment CR.
> Add validation for the name of FlinkDeployment CR
> -------------------------------------------------
>
> Key: FLINK-28087
> URL: https://issues.apache.org/jira/browse/FLINK-28087
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Fred k
> Assignee: Fred k
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.1.0
>
> Attachments: operator-flink.jpg
>
>
> The name of FlinkDeployment CR meta.name must be match the regex:
> {code:java}
> '[a-z]([-a-z0-9]{0,43}[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|https://github.com/apache/flink-kubernetes-operator/pull/%5B-a-z0-9%5D*%5Ba-z0-9%5D]?').
> The rest service name of Flink Cluster uses the meta.name of FlinkDeployment
> CR, So the value of meta.name must follow the convention of DNS-1035 label.
> The length of the value of name must be no more than 45 characters. See
> [Limit the value of kubernetes.cluster-id to have no more than 45 characters
> |https://github.com/apache/flink/pull/11708]
> To avoid operator repeatedly creating and destroying flink clusters due to
> invalid service name, So I suggest add validation for the name of
> FlinkDeployment CR.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
