helm kubernetes events.k8s.io/v1 deprecated fields

[amayacitta]

K8s: v1.31.4
otel collector chart: opentelemetry-collector-0.118.0

When using the presents for k8-events as outlined below.

mode: deployment
replicaCount: 1
presets:
kubernetesEvents:
enabled: true

The logs that are exported show depricated use of the api for the following fields.

• deprecatedCount
• deprecatedFirstTimestamp
• deprecatedLastTimestamp
• deprecatedSource

According to here, the correct fields are below as of v1.25. We are running v.1.31.4

• deprecatedCount = series.count
• deprecatedFirstTimestamp = eventTime
• deprecatedLastTimestamp = series.lastObservedTime
• deprecatedSource = reportingController

Here is an example log line exported using the presents.

{"object":{"apiVersion":"events.k8s.io/v1","deprecatedCount":1,"deprecatedFirstTimestamp":"2025-03-17T09:22:27Z","deprecatedLastTimestamp":"2025-03-17T09:22:27Z","deprecatedSource":{"component":"replicaset-controller"},"eventTime":null,"kind":"Event","metadata":{"creationTimestamp":"2025-03-17T09:22:27Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:reportingComponent":{},"f:source":{"f:component":{}},"f:type":{}},"manager":"kube-controller-manager","operation":"Update","time":"2025-03-17T09:22:27Z"}],"name":"k8s-events-opentelemetry-collector-575cccdf7.182d8cb6cbb4091c","namespace":"infra-logs","resourceVersion":"54069092","uid":"e9c429ad-893c-4751-8a7b-c51e87154e6b"},"note":"Deleted pod: k8s-events-opentelemetry-collector-575cccdf7-wwqdz","reason":"SuccessfulDelete","regarding":{"apiVersion":"apps/v1","kind":"ReplicaSet","name":"k8s-events-opentelemetry-collector-575cccdf7","namespace":"infra-logs","resourceVersion":"54069086","uid":"57e897d4-5da9-4b7f-ad73-1146288d90ac"},"reportingController":"replicaset-controller","type":"Normal"},"type":"ADDED"}

[github-actions]

Pinging code owners for receiver/k8sobjectsreceiver: @dmitryax @hvaghani221 @TylerHelmuth @ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[TylerHelmuth]

@amayacitta the k8sobjectreceiver doesn't do any manipulation of the logs it receives so these values are coming from k8s.

I do wonder if the receiver's client is outdated or if it is using an old client?

The helm chart's preset sets

receivers:
  k8sobjects:
    objects:
      - name: events
        mode: "watch"
        group: "events.k8s.io"
        exclude_watch_type:
          - "DELETED"

and as far as I know that is still the proper group.

[amayacitta]

Yep, the config map from the default preset deployment on mine shows the below. As of now I'm running Kubernetes version v1.32.0.

I'm running helm chart opentelemetry-collector-0.119.0, app version 0.121.0.

I'm using is the vanilla presets as described. Is there anything else we can check?

receivers:
  k8sobjects:
    objects:
    - exclude_watch_type:
      - DELETED
      group: events.k8s.io
      mode: watch
      name: events