From c08a67d88e97cdfc5da183358141e611e64136c6 Mon Sep 17 00:00:00 2001 From: Mukul Sharma Date: Sat, 12 Sep 2026 15:24:54 +0530 Subject: [PATCH] Server-side apply for the argocd Application MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Argo CD v3's own CRDs (applications, applicationsets, appprojects) embed large schemas that exceed the 256KiB last-applied-configuration annotation a client-side apply writes — the same reason cert-manager and external-secrets already use this. Without it the upgrade sync fails on the CRDs rather than on anything in the release. ServerSideDiff comes with it for the same reason as the other three, and becomes belt-and-braces once the upgraded Argo CD's schema matches the cluster. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N --- .../incubator-infra-gke-toolshed-prd-usc1-values.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/values/incubator-infra-gke-toolshed-prd-usc1-values.yaml b/values/incubator-infra-gke-toolshed-prd-usc1-values.yaml index 9eb8c10..d3521eb 100644 --- a/values/incubator-infra-gke-toolshed-prd-usc1-values.yaml +++ b/values/incubator-infra-gke-toolshed-prd-usc1-values.yaml @@ -34,6 +34,16 @@ appSpec: namespace: argocd chartDir: argo-cd valuesDir: argocd-admin-prd + # Argo CD v3's own CRDs (applications, applicationsets, appprojects) + # embed large schemas, past the 256KiB last-applied-configuration limit + # a client-side apply writes — the same reason cert-manager and + # external-secrets use this. + serverSideApply: true + # And therefore the same stale-schema diff problem: see the contour + # entry. Once the upgrade lands, Argo CD's schema matches this cluster + # and this becomes belt-and-braces rather than load-bearing. + compareOptions: + - ServerSideDiff=true - name: gitea nameOverride: gitea namespace: gitea