Configure the OpenTelemetry Collector k8sobjects receiver to pull Kubernetes events and objects as logs

Steps

1. Add a k8s_objects receiver block under receivers (the YAML component key is k8s_objects, distinct from the package name k8sobjectsreceiver), setting auth_type to serviceAccount (default), kubeConfig, or none.
2. Under objects, list one entry per resource type to collect (e.g. pods, events, nodes), each with name and mode: pull or mode: watch, plus optional label_selector, field_selector, namespaces, and exclude_namespaces filters.
3. For pull-mode objects, set a per-object interval (falls back to the receiver-level interval, default 1h, if unset); for watch-mode objects, optionally set resource_version and include_initial_state to control watch startup behavior.
4. Grant the Collector's ServiceAccount a ClusterRole with get/list/watch verbs on the targeted resources — list is required even in watch mode for the initial listing and for recovering from HTTP 410 Gone responses — and bind it via a ClusterRoleBinding.
5. Optionally set storage: <file_storage extension id> so the receiver persists each watch-mode object's resourceVersion across restarts (pull-mode is unaffected), and k8s_leader_elector: <k8sleaderelector extension id> to safely run multiple replicas.
6. Add k8s_objects to a logs pipeline under service.pipelines.logs.receivers, and deploy the Collector as a single-replica Deployment unless k8s_leader_elector is configured, to avoid duplicated log events.