-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
Decide whether to remove resources
from the codebase
#5785
Comments
AI:
|
JeromeJu
changed the title
Removal of
Decide wether to remove Nov 28, 2022
resources
from the codebaseresources
from the codebase
JeromeJu
changed the title
Decide wether to remove
Decide whether to remove Nov 28, 2022
resources
from the codebaseresources
from the codebase
Closing as the consensus is reached during WG and #5805 is created as a follow up issue of the AI |
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is opened for further discussion about whether we should remove the
resources
-related fields and respective supports. The current approach we went for includes keeping the deprecatedresources
and its related fields where it has been serialized in the conversions. However, this is brought up to discussion in the PR when releasing V1 CRD.The goal of this issue is to make sure that the V1 release can move forward after reaching a consensus on whether we should keep the current route for keeping the
resources
related fields.Thanks to @pritidesai @vdemeester and @lbernick for the discussion at the v1-CRD-release PR #5579 (comment)_
Related discussions:
The text was updated successfully, but these errors were encountered: