Add configurable list of fields to remove from object before storing and reduce DB storage use

[enarha]

Feature request

Currently Results store the objects as is. On retrieving from the DB we can filter and return a subset of the fields, but in general everything is stored and that consumes DB storage. One optimization to do is filter out managedfields before the object is stored, maybe some other fields as well. That should be user configurable and opt-in feature.
The Tekton Pipeline controller does something similar to improve the memory footprint here (tektoncd/pipeline#9316).

Use case