From 9197bb28b993cd2a40eb221f4b8f5611c29d04cc Mon Sep 17 00:00:00 2001 From: Evgen Karlashov Date: Fri, 8 Jul 2022 11:07:18 +0200 Subject: [PATCH] Changes to customresourcestate doc Signed-off-by: Evgen Karlashov --- docs/customresourcestate-metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/customresourcestate-metrics.md b/docs/customresourcestate-metrics.md index 935d54ec..6442c322 100644 --- a/docs/customresourcestate-metrics.md +++ b/docs/customresourcestate-metrics.md @@ -14,7 +14,7 @@ Two flags can be used: If both flags are provided, the inline configuration will take precedence. -Apart from specifying one of `--custom-resource-state-config-*` flags, you also need to add a custom resource *Kind* in plural form to the list of existing resources in `--resources` flag. If you don't specify `--resources`, then `--custom-resource-state-config-*` and all available default kubernetes objects will be taken into accout by kube-state-metrics. +In addition to specifying one of `--custom-resource-state-config*` flags, you should also add the custom resource *Kind*s in plural form to the list of exposed resources in the `--resources` flag. If you don't specify `--resources`, then all known custom resources configured in `--custom-resource-state-config-*` and all available default kubernetes objects will be taken into account by kube-state-metrics. ```yaml apiVersion: apps/v1