• Test the library-go’s resourceapply utils with caching enabled.
• Investigate that CMO “memory leak” mentionedin https://docs.google.com/document/d/1fm2SZs8HroexPQnqI0Ua85Y31-lars8gCsdwSJC3ngo/edit?usp=sharing.
• See if we could avoid running new WATCHes per sync + See why GET count is reduced in https://docs.google.com/document/d/1fm2SZs8HroexPQnqI0Ua85Y31-lars8gCsdwSJC3ngo/edit?usp=sharing

See "Next steps" https://docs.google.com/document/d/1fm2SZs8HroexPQnqI0Ua85Y31-lars8gCsdwSJC3ngo/edit?usp=sharing for more details.

Split this into tasks if needed.