Peter Jiang

@rajatvig @blakepettersson From my understanding this can be fixed by allowing argocd-controller to take ownership of the field you want to remove by re-declaring it with Argo CD’s field manager...

Closing due to https://github.com/argoproj/gitops-engine/pull/735

this looks like a duplicate of https://github.com/argoproj/argo-cd/issues/18038

Tested this on the UI and it seems to be behaving as expected. Only when we use the CLI its giving this output: UI: CLI: ``` argocd app diff svc-ssd...

@klaudworks Do you mind showing the complete resource with its managed fields? My guess is the operator manages the fields instead of argo cd.

@klaudworks Looking at your example, the field you are describing that doesn't show a diff is indeed owned by another controller/operator ``` f:ingress: {} manager: nginx-ingress-controller ``` This means argocd...

> @pjiang-dev @crenshaw-dev could we not do something similar as [kubernetes/kubernetes#124191](https://github.com/kubernetes/kubernetes/pull/124191) where we'd force ownership of all fields, given that we opt-in to this behavior by adding another sync option?...

> provide an additional annotation with SSA that allows users to specify their own field manager to migrate fields. This would replace the 'kubectl-client-side-apply' field manager in this PR with...

For this PR i will leave as is and create a follow up PR to make the field manager to migrate fields configurable to the user

> > For this PR i will leave as is and create a follow up PR to make the field manager to migrate fields configurable to the user > >...