In future (k8s v1.35) going to support officially comparable resources versions:
kubernetes/enhancements#5505

This has implications on our implementations - we already support this with feature flag (by default turned off) in informer temporary caches. But we will be able to optimize better for example in PrimaryUpdateAndCacheUtils - that would no longer require to do the update through optimistic locking.

• how to support non complient resources. Automatic detection vs explicit configuration. -> explicit per informer event source
• which version to ship? (basically this is supported also now in Kubernetes so we might target 5.2+) -> 5.3
• Identify all the improvements we can do based on this. (some PR-s already added) -> see sub tasks and PRs here
• review if on event lockstriping can be relaxed more
• concurrent modification support on event filtering

Notes:

• related issue in controller runtime: Idea: Provide read your own write for the cache-backed client kubernetes-sigs/controller-runtime#3320
• https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/5647-stale-controller-handling