Skip to content

Commit 9117178

Browse files
authored
Namespace names must be RFC 1123 DNS labels
The how-to docs to create a new namespace already specify this, but I think it's worth mentioning in the overview doc that a namespace name must be an RFC 1123 label, as I didn't initially think to look in the how-to doc for limitations.
1 parent 66081ef commit 9117178

File tree

1 file changed

+3
-0
lines changed
  • content/en/docs/concepts/overview/working-with-objects

1 file changed

+3
-0
lines changed

content/en/docs/concepts/overview/working-with-objects/namespaces.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,9 @@ is local to a namespace. This is useful for using the same configuration across
9898
multiple namespaces such as Development, Staging and Production. If you want to reach
9999
across namespaces, you need to use the fully qualified domain name (FQDN).
100100

101+
As a result, all namespace names must be valid
102+
[RFC 1123 DNS labels](/docs/concepts/overview/working-with-objects/names/#dns-label-names).
103+
101104
## Not All Objects are in a Namespace
102105

103106
Most Kubernetes resources (e.g. pods, services, replication controllers, and others) are

0 commit comments

Comments
 (0)