From e0f55762dcef725685176708d9e89915bd0a66a9 Mon Sep 17 00:00:00 2001 From: Haoran Wang Date: Wed, 12 Jun 2019 21:55:31 +0800 Subject: [PATCH] Update field-selectors.md (#14839) We should use --all-namespaces to filter all the service --- .../concepts/overview/working-with-objects/field-selectors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/working-with-objects/field-selectors.md b/content/en/docs/concepts/overview/working-with-objects/field-selectors.md index 637af3ad92..d4e02418e5 100644 --- a/content/en/docs/concepts/overview/working-with-objects/field-selectors.md +++ b/content/en/docs/concepts/overview/working-with-objects/field-selectors.md @@ -40,7 +40,7 @@ Error from server (BadRequest): Unable to find "ingresses" that match label sele You can use the `=`, `==`, and `!=` operators with field selectors (`=` and `==` mean the same thing). This `kubectl` command, for example, selects all Kubernetes Services that aren't in the `default` namespace: ```shell -kubectl get services --field-selector metadata.namespace!=default +kubectl get services --all-namespaces --field-selector metadata.namespace!=default ``` ## Chained selectors