All 29 Sync & Health questions
More in Sync & Health
What happens during a sync when a resource apply fails? How does ArgoCD assess Deployment health specifically? What is the Suspended health status? How do you skip health assessment or diff for specific fields? How do you handle CRDs and their custom resources syncing in the right order? How can you customize health checks for third-party or custom resources? How do you implement progressive delivery (canary/blue-green) with ArgoCD? How do you prevent auto-sync from applying an unwanted change during an incident? How do you monitor ArgoCD itself (metrics and observability)? How do you debug why an app never reaches Healthy after a successful sync?
Advertisement
Back to results for “Resources”
ArgoCD › Sync & Health

How does ServerSideApply help with large or conflicting resources?

Advanced

Answer

Server-Side Apply (SSA) lets Kubernetes merge changes field-by-field with ownership tracking, avoiding the last-applied-configuration annotation size limits (e.g., large CRDs) and reducing conflicts when multiple controllers manage different fields. ArgoCD can use SSA per-sync or per-resource to apply big CRDs and coexist with other field managers.
metadata:
  annotations:
    argocd.argoproj.io/sync-options: ServerSideApply=true
Real-world example A very large CRD that failed client-side apply due to annotation size limits applies cleanly with ServerSideApply.

Common follow-ups: What limit does SSA avoid? | How does SSA handle field ownership?

Applications Sync Waves & Hooks Sync & Health
All 29 Sync & Health questions