Event model and api mismatch.

[iocanel]

It seems that client.v1().events().list() return io.fabric8.kubernetes.api.model.Event while I would expect it to return it's v1 variant.

[rohanKanojia]

Umm, client.v1().events() provides Event class from kubernetes/api (which is used in kubectl get events). Are you talking about events.k8s.io/v1#Event ? I think we are missing DSL support for this.

[iocanel]

I would expect v1().events() to operate on events.v1, is my assumption wrong?

[manusa]

As Rohan says, this DSL v1() points to core.v1 K8s API.
The events() method within the V1APIGroupDSL provides access to the Event v1 core resource (/api/v1/namespaces/{namespace}/events).

I think you are referring to the v1 Events API introduced in Kubernetes 1.19.

I would expect v1().events() to operate on events.v1, is my assumption wrong?

My assumption would be to access the events API through events().v1() or events().v1beta1(), but unfortunately those interfaces are missing :(. Also the model package/module should be different too.

---

So just to be clear, since this confuses many users and we probably need to figure out a way to make it clearer:

• There are events in the core.v1 K8s API
• There are events in the events.v1 and events.v1beta1 K8s API (apparently, currently unsupported)
• There are WatchEvents provided by the Watch REST API spec.