From 7e7170cecbf2bdb6b8172dc556c5c9db3fa9f7c3 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Sun, 27 Aug 2017 18:25:45 +0800 Subject: [PATCH] Update namespaces.md Missing signal. --- docs/concepts/overview/working-with-objects/namespaces.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/overview/working-with-objects/namespaces.md b/docs/concepts/overview/working-with-objects/namespaces.md index 0f66878964..aa06eff515 100644 --- a/docs/concepts/overview/working-with-objects/namespaces.md +++ b/docs/concepts/overview/working-with-objects/namespaces.md @@ -30,7 +30,7 @@ resources within the same namespace. ## Working with Namespaces Creation and deletion of namespaces is described in the [Admin Guide documentation -for namespaces](/docs/admin/namespaces) +for namespaces](/docs/admin/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). This entry is of the form `..svc.cluster.local`, which means -that if a container just uses `` it will resolve to the service which +that if a container just uses ``, it will resolve to the service which 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 across namespaces, you need to use the fully qualified domain name (FQDN).