David Heredero

@clayvan We had the same problem on our Deployments and managed to fix the issue using the `knownTypeFields` parameter in the `argo-cm` configmap: ```yaml resource.customizations.knownTypeFields.apps_Deployment: | - field: spec.template.spec type:...