Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feature: remove community parsing of resource versions #2457

Open
1 task
stevekuznetsov opened this issue Dec 7, 2022 · 1 comment
Open
1 task

feature: remove community parsing of resource versions #2457

stevekuznetsov opened this issue Dec 7, 2022 · 1 comment
Assignees
@stevekuznetsov
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stevekuznetsov
Copy link
Contributor

Feature Description

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.

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response
@stevekuznetsov stevekuznetsov added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 7, 2022
@stevekuznetsov stevekuznetsov self-assigned this Dec 7, 2022
@stevekuznetsov
Copy link
Contributor Author

xref #1022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevekuznetsov stevekuznetsov

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
kcp
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stevekuznetsov