Decide whether to remove resources from the codebase

[JeromeJu]

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 deprecated resources 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:

• Handle deprecated fields during conversion from v1beta1 to v1 #4546
• TEP-0074
• TEP-0105 to remove v1alpha1
• were proposed in API WG

[JeromeJu]

AI:

• To make sure there are Validations on the annotations when converting down from v1 to v1beta1

To be put in code review:
To have documentations on the conversion of annotations, and about how it will get dropped later

[JeromeJu]

Closing as the consensus is reached during WG and resources will be kept supported in the code base while being serialized into annotations when converted to v1.

#5805 is created as a follow up issue of the AI