kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1572 from atlassian/namespace-identifier 

Namespace is a DNS_LABEL
This commit is contained in:
k8s-ci-robot 2018-01-22 10:49:35 -08:00 committed by GitHub
parent c4e919fbbe 0505c23145
commit 13140d520b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
contributors/design-proposals/architecture/identifiers.md
View File

@ -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. impractical, some or all objects may support a param to auto-generate a name.
Generating random names will defeat idempotency. Generating random names will defeat idempotency.
* Examples: "guestbook.user", "backend-x4eb1" * Examples: "guestbook.user", "backend-x4eb1"
2. When an object is created via an API, a Namespace string (a DNS_SUBDOMAIN? 2. When an object is created via an API, a Namespace string (a DNS_LABEL)
format TBD via #1114) may be specified. Depending on the API receiver, may be specified. Depending on the API receiver,
namespaces might be validated (e.g. apiserver might ensure that the namespace 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 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. API receiver. This assignment policy might vary across API receivers (e.g.