Repository navigation
Epic: API evolution #1671
Description
- Add fields to APIResourceSchema that contain CEL that is called during API version conversion
- Add CEL converter to apiextensions-apiserver
- Bound CRDs will need a way to point back at the actual CEL (annotation?)
- Conversions must go through a single hub version
- Feature gated
Demo:
kubectl applyyaml with v1alpha1kubectl getreturns v1alpha2, see results of conversion
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]API evolution[/-][+]Epic: API evolution[/+]pweil- commentedon Aug 24, 2022
0.8 Check in here. I don't see anything scoped per milestone, can we break down this epic more to see what is expected when? Thanks!
ncdc commentedon Aug 24, 2022
I started looking into this before my PTO. I will get it updated this week. Going to move to 0.9 for the time being.
/milestone v0.9
ncdc commentedon Aug 31, 2022
Started some API brainstorming https://hackmd.io/_EnPemBUTF-b7WFs8o6Gjw
stevekuznetsov commentedon Dec 14, 2022
This has been subsumed by #2014
/close
openshift-ci commentedon Dec 14, 2022
@stevekuznetsov: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.