diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-01-22 10:49:35 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-22 10:49:35 -0800 |
| commit | 13140d520bf9230298b6d1f272d849a5426decd5 (patch) | |
| tree | d05d8c073390e61c62bf6d41196bb550dbb8d4e8 | |
| parent | c4e919fbbe2928829fa8047f06614272fc1d6ed8 (diff) | |
| parent | 0505c231458107e3d83bf6fb990d24f67156f86e (diff) | |
Merge pull request #1572 from atlassian/namespace-identifier
Namespace is a DNS_LABEL
| -rw-r--r-- | contributors/design-proposals/architecture/identifiers.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/architecture/identifiers.md b/contributors/design-proposals/architecture/identifiers.md index 977c0c99..3b872481 100644 --- a/contributors/design-proposals/architecture/identifiers.md +++ b/contributors/design-proposals/architecture/identifiers.md @@ -55,8 +55,8 @@ suffix) to create a unique Name. For situations where generating a name is impractical, some or all objects may support a param to auto-generate a name. Generating random names will defeat idempotency. * Examples: "guestbook.user", "backend-x4eb1" -2. When an object is created via an API, a Namespace string (a DNS_SUBDOMAIN? -format TBD via #1114) may be specified. Depending on the API receiver, +2. When an object is created via an API, a Namespace string (a DNS_LABEL) +may be specified. Depending on the API receiver, namespaces might be validated (e.g. apiserver might ensure that the namespace actually exists). If a namespace is not specified, one will be assigned by the API receiver. This assignment policy might vary across API receivers (e.g. |