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

Add 'svc.' before 'cluster.local' and fix some typos 

1. Add 'svc.' before 'cluster.local'
2. ```Terminating`` to `Terminating`
3. 'DNS entry1' to 'DNS entry'
pull/6/head
qiaolei 2015-09-06 10:45:46 +08:00 committed by hw-qiaolei
parent e6e69e31ec
commit 41708fb0af
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/admin/namespaces.md
View File

@ -122,7 +122,7 @@ See [Admission control: Limit Range](../design/admission_control_limit_range.md)
A namespace can be in one of two phases: A namespace can be in one of two phases:
* `Active` the namespace is in use * `Active` the namespace is in use
* ```Terminating`` the namespace is being deleted, and can not be used for new objects * `Terminating` the namespace is being deleted, and can not be used for new objects
See the [design doc](../design/namespaces.md#phases) for more details. See the [design doc](../design/namespaces.md#phases) for more details.
@ -166,8 +166,8 @@ This delete is asynchronous, so for a time you will see the namespace in the `Te
## Namespaces and DNS ## Namespaces and DNS
When you create a [Service](../../docs/user-guide/services.md), it creates a corresponding [DNS entry](dns.md)1. When you create a [Service](../../docs/user-guide/services.md), it creates a corresponding [DNS entry](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>.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

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

@ -105,7 +105,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). 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>.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