[Core][Performance] Clear managed fields from FlyteWorkflow CRD

[hamersaw]

Motivation: Why do you think this is important?

K8s tracked managed fields as a way to ensure some level of access control over resources. The FlyteWorkflow is one such resource. However, flyte ensures that each FlyteWorkflow is only managed by a single FlytePropeller instance. Therefore, managed fields are unnecessary.

In the general case this is not an issue, but in the case of large workflows (ie. many nodes), which may result from large fanout dynamic tasks among other phenomena, the managed fields can bloat CRDs by 100's of KB. Etcd read / write performance is often contingent on small key / value pairs and degradation over large values is a known issue.

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

Managed fields should be cleared on all FlyteWorkflow CRDs.

Describe alternatives you've considered

Existing approach is to leave the managed fields.

Propose: Link/Inline OR Additional context

No response

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

• Yes

Have you read the Code of Conduct?

• Yes