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

Merge pull request #5218 from stewart-yu/patch-44 

Update namespaces.md
pull/5273/head
Andrew Chen 2017-09-01 16:39:45 -07:00 committed by GitHub
parent a4016b1a5f 7e7170cecb
commit b59e0e7f98
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/concepts/overview/working-with-objects/namespaces.md
View File

@ -30,7 +30,7 @@ resources within the same namespace.
## Working with Namespaces ## Working with Namespaces
Creation and deletion of namespaces is described in the [Admin Guide documentation Creation and deletion of namespaces is described in the [Admin Guide documentation
for namespaces](/docs/admin/namespaces) for namespaces](/docs/admin/namespaces).
### Viewing namespaces ### Viewing namespaces
@ -74,7 +74,7 @@ $ kubectl config view | grep namespace:
When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns). When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
that if a container just uses `<service-name>` it will resolve to the service which that if a container just uses `<service-name>`, it will resolve to the service which
is local to a namespace. This is useful for using the same configuration across is local to a namespace. This is useful for using the same configuration across
multiple namespaces such as Development, Staging and Production. If you want to reach multiple namespaces such as Development, Staging and Production. If you want to reach
across namespaces, you need to use the fully qualified domain name (FQDN). across namespaces, you need to use the fully qualified domain name (FQDN).