[Core feature] Support CRD Migration

[EngHabu]

Motivation: Why do you think this is important?

FlyteWorkflow CRD has grown complex. In many cases losing the advantage of Protobuf backward compatibility because it uses json to marshal/unmarshal fields requiring names to match, fields to exist... etc. In addition, because of json marshaling, it makes the size of the CRD much larger than the actual data stored in it...

Goal: What should the final outcome look like, ideally?

A way to move from v1alpha1 CRD version to a newer version, we should be able to write code somewhere that takes care of the translation between a version and the next one, check that in and magic happens at runtime.. maybe the actual execution code in Propeller should always only need to handle the latest version.

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

Official Docs

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[hamersaw]

Commenting to keep open.

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏