github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #13304 from alexwlchan/patch-1 

Fix typos in namespaces.md
pull/6/head
Jerzy Szczepkowski 2015-08-31 09:19:35 +02:00
parent 86fb79da05 60dc440bda
commit 3f1a94f48f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/user-guide/namespaces.md
View File

@ -45,7 +45,7 @@ need the features they provide.
Namespaces provide a scope for names. Names of resources need to be unique within a namespace, but not across namespaces. Namespaces provide a scope for names. Names of resources need to be unique within a namespace, but not across namespaces.
Namespaces are a way to divide cluster resources between multiple uses (via [resource quota])(../../docs/admin/resource-quota.md). Namespaces are a way to divide cluster resources between multiple uses (via [resource quota](../../docs/admin/resource-quota.md)).
In future versions of Kubernetes, objects in the same namespace will have the same In future versions of Kubernetes, objects in the same namespace will have the same
access control policies by default. access control policies by default.
@ -57,7 +57,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.md) for namespaces](../../docs/admin/namespaces.md)
### Viewing namespaces ### Viewing namespaces
@ -104,7 +104,7 @@ $ kubectl config set-context $(CONTEXT) --namespace=<insert-namespace-name-here>
## Namespaces and DNS ## Namespaces and DNS
When you create a [Service](services.md), it creates a corresponding [DNS entry](../admin/dns.md)1. When you create a [Service](services.md), it creates a corresponding [DNS entry](../admin/dns.md).
This entry is of the form `<service-name>.<namespace-name>.cluster.local`, which means This entry is of the form `<service-name>.<namespace-name>.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