Argo CD validating duplicate variables and causing sync issues about argo-cd

[brunokino]

This discussion is related to this Issue:
#17784

[agaudreault]

So from my understanding, if Kubernetes does not return an error on duplicated values and it is a valid live manifest, I think Argo should handle to diff and sync manifest with duplicated values.

If you can open a pull request, I think it will be a good contribution 👍

[agaudreault]

You mention

I expected that argocd would be able to sync the application even with duplicate variables because kubernetes only blocks this operation if applied with Server Side Apply, but even when applied without serverSideApply, argocd returns an error.

Is there a way to make it fail the first time when argocd will sync without server-side apply?

Or does this happen when existing live manifest not deployed from Argo have duplicated entries in their spec?

[brunokino]

@agaudreault ,

The problem occurs with live manifest created before adding the mentioned configuration

resource.customizations.ignoreDifferences.all: |-
  managedFieldsManagers:
  - kube-controller-manager

This configuration is manually added by ScaleOps, which is a continuous workload optimization tool.

However, once the manifest with duplicate variable exists and the configuration has been applied, users are not able to sync their applications and even remove the duplicate variable by themselves via GitOps, it needs an admin to remove it from the live manifest first.

In our company, we had to make a script to remove duplicates from all objects via kubectl. After that, users stop getting the TypedLive error and start getting a TypeConfig error during sync, but this time they are able to remove the duplication in git and continue with the Sync.