During the migration we ran across a weird use-case for K8sPatch call. The patches are compact and then checked for still having valid ones. This is a weird pattern for the API call. This is a quirk of the caller code and thus should be owned by the caller code.

Acceptance Criteria

• K8sPatchCode has functionality to sanitize the result, and that should not in the Core SDK so we need to make sure when we migrate back it pushes this functionality onto the App