From 5522e5ddf93c4bea0b84a207a56ceff8fdaeb205 Mon Sep 17 00:00:00 2001 From: Luzhenxing Date: Tue, 5 Nov 2019 14:24:38 +0800 Subject: [PATCH] add the same namespace (#17394) --- .../en/docs/concepts/overview/working-with-objects/names.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/overview/working-with-objects/names.md b/content/en/docs/concepts/overview/working-with-objects/names.md index ab526c796c..af24d5f184 100644 --- a/content/en/docs/concepts/overview/working-with-objects/names.md +++ b/content/en/docs/concepts/overview/working-with-objects/names.md @@ -12,8 +12,7 @@ weight: 20 Each object in your cluster has a [_Name_](#names) that is unique for that type of resource. Every Kubernetes object also has a [_UID_](#uids) that is unique across your whole cluster. -For example, you can only have one Pod named “myapp-1234”, but you can have one Pod -and one Deployment that are each named “myapp-1234”. +For example, you can only have one Pod named `myapp-1234` within the same [namespace](/docs/concepts/overview/working-with-objects/namespaces/), but you can have one Pod and one Deployment that are each named `myapp-1234`. For non-unique user-provided attributes, Kubernetes provides [labels](/docs/concepts/overview/working-with-objects/labels/) and [annotations](/docs/concepts/overview/working-with-objects/annotations/).