diff --git a/.chloggen/k8sobject-handle-410.yaml b/.chloggen/k8sobject-handle-410.yaml new file mode 100755 index 000000000000..ad5c581716c2 --- /dev/null +++ b/.chloggen/k8sobject-handle-410.yaml @@ -0,0 +1,27 @@ +# Use this changelog template to create an entry for release notes. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: enhancement + +# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) +component: k8sobjectsreceiver + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: Adds logic to properly handle 410 response codes when watching. This improves the reliability of the receiver. + +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. +issues: [26098] + +# (Optional) One or more lines of additional information to render under the primary note. +# These lines will be padded with 2 spaces and then inserted directly into the document. +# Use pipe (|) for multiline entries. +subtext: + +# If your change doesn't affect end users or the exported elements of any package, +# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. +# Optional: The change log or logs in which this entry should be included. +# e.g. '[user]' or '[user, api]' +# Include 'user' if the change is relevant to end users. +# Include 'api' if there is a change to a library API. +# Default: '[user]' +change_logs: [] diff --git a/receiver/k8sobjectsreceiver/README.md b/receiver/k8sobjectsreceiver/README.md index 97de9470a24e..c7902f03fb2a 100644 --- a/receiver/k8sobjectsreceiver/README.md +++ b/receiver/k8sobjectsreceiver/README.md @@ -122,7 +122,8 @@ Use the below commands to create a `ClusterRole` with required permissions and a Following config will work for collecting pods and events only. You need to add appropriate rule for collecting other objects. -When using watch mode without specifying a `resource_version` you must also specify `list` verb so that the receiver has permission to do its initial list. +When using watch mode you must also specify `list` verb so that the receiver has permission to do its initial list if no +`resource_version` was supplied or a list to recover from [410 Gone scenarios](https://kubernetes.io/docs/reference/using-api/api-concepts/#410-gone-responses). ```bash <