From f3348e73a25310c1f44960de009c24e98a436c45 Mon Sep 17 00:00:00 2001 From: Alexander Held Date: Mon, 28 Oct 2024 16:56:33 +0100 Subject: [PATCH] [chore] make pull/poll working more consistent (#35974) #### Description I noticed, that in this file, you are using pull and poll synonymous at a config explanation. I agree they kinda are, but it may confuse people if they don't read further. Therefore I propose, that we change this to only use the term we expect in the configuration. --- receiver/k8sobjectsreceiver/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/receiver/k8sobjectsreceiver/README.md b/receiver/k8sobjectsreceiver/README.md index 363be572f061..c08019ff1925 100644 --- a/receiver/k8sobjectsreceiver/README.md +++ b/receiver/k8sobjectsreceiver/README.md @@ -43,7 +43,7 @@ the K8s API server. This can be one of `none` (for no auth), `serviceAccount` (to use the standard service account token provided to the agent pod), or `kubeConfig` to use credentials from `~/.kube/config`. - `name`: Name of the resource object to collect -- `mode`: define in which way it collects this type of object, either "poll" or "watch". +- `mode`: define in which way it collects this type of object, either "pull" or "watch". - `pull` mode will read all objects of this type use the list API at an interval. - `watch` mode will do setup a long connection using the watch API to just get updates. - `label_selector`: select objects by label(s)