You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add resourceSchemas new field, which would be used in favor of latestResourceSchemas field.
Anything added to the latestResourceSchemas field would be automatically added to resourceSchemas via mutation and set to storage: CRD. The latestResourceShemas field would be marked as deprecated, and resource schemas would be the source of truth. Bump API version by minor version
Alternative Solutions
No response
Want to contribute?
I would like to work on this issue.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Following https://docs.google.com/document/d/18Xh2-VFnH23bDiAHPP_JXm4qAG4QK6GjTKcpszPGApQ/edit?tab=t.0
This is the first ticket in the implementation list.
Epic: #3292
Proposed Solution
Add resourceSchemas new field, which would be used in favor of latestResourceSchemas field.
Anything added to the latestResourceSchemas field would be automatically added to
resourceSchemas
via mutation and set to storage: CRD. The latestResourceShemas field would be marked as deprecated, and resource schemas would be the source of truth. Bump API version by minor versionAlternative Solutions
No response
Want to contribute?
Additional Context
No response
The text was updated successfully, but these errors were encountered: