Skip to content

Commit c14b7f4

Browse files
Merge pull request #289 from sibucan/lke-labels
[Update] lke/clusters PUT and lke/cluster POST to reflect actual behavior
2 parents e4d8cca + e841631 commit c14b7f4

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

openapi.yaml

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16010,14 +16010,19 @@ components:
1601016010

1601116011
Labels have the following constraints:
1601216012

16013-
* Must start with an alpha character
16014-
* Must only consist of alphanumeric characters and dashes (`-`)
16015-
* Must not contain two dashes in a row
16016-
minLength: 3
16013+
* UTF-8 characters will be returned by the API using escape
16014+
sequences of their Unicode code points. For example, the
16015+
Japanese character *か* is 3 bytes in UTF-8 (`0xE382AB`). Its
16016+
Unicode code point is 2 bytes (`0x30AB`). APIv4 supports this
16017+
character and the API will return it as the escape sequence
16018+
using six 1 byte characters which represent 2 bytes of Unicode
16019+
code point (`"\u30ab"`).
16020+
* 4 byte UTF-8 characters are not supported.
16021+
* If the label is entirely composed of UTF-8 characters, the API
16022+
response will return the code points using up to 193 1 byte
16023+
characters.
16024+
minLength: 1
1601716025
maxLength: 32
16018-
# Kubernetes does NOT allow underscores in resource names and we are
16019-
# passing this name to Kubernetes. Thus the following pattern:
16020-
pattern: '[a-zA-Z0-9-]{3, 32}'
1602116026
x-linode-cli-display: 2
1602216027
example: lkecluster12345
1602316028
region:

0 commit comments

Comments
 (0)