Tightly coupling the .metadata.resourceVersion to etcd semantics would make a CRDB storage implementation more challenging. Any effort to change the semantics of the field (or make it fully opaque) hinge on how many users in the wild are actually parsing it. A review found a few, which we need to fix, listed here.
Proposed Solution
Each case has a slightly different fix, but they are all listed.
stevekuznetsov
commented
1 year ago
Feature Description
Tightly coupling the
.metadata.resourceVersiontoetcdsemantics would make a CRDB storage implementation more challenging. Any effort to change the semantics of the field (or make it fully opaque) hinge on how many users in the wild are actually parsing it. A review found a few, which we need to fix, listed here.Proposed Solution
Each case has a slightly different fix, but they are all listed.
Alternative Solutions
No response
Want to contribute?
Additional Context
No response