From 2f6093bfd733df2e66763e27a95dcfdb09846ff7 Mon Sep 17 00:00:00 2001 From: Sebastian Winkler Date: Mon, 8 Jun 2020 19:10:26 +0200 Subject: [PATCH] workaround for new lines in field selector example --- .../overview/working-with-objects/field-selectors.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) 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 44cd54e72f..45a81e9035 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 @@ -16,12 +16,7 @@ kubectl get pods --field-selector status.phase=Running ``` {{< note >}} -Field selectors are essentially resource *filters*. By default, no selectors/filters are applied, meaning that all resources of the specified type are selected. This makes the following `kubectl` queries equivalent: - -```shell -kubectl get pods -kubectl get pods --field-selector "" -``` +Field selectors are essentially resource *filters*. By default, no selectors/filters are applied, meaning that all resources of the specified type are selected. This makes the `kubectl` queries `kubectl get pods` and `kubectl get pods --field-selector ""` equivalent. {{< /note >}} ## Supported fields