From 91b32407f8b046dd8959a8e16774b2815fb2ea9d Mon Sep 17 00:00:00 2001
From: Nikholas Pcenicni <82239765+nikpcenicni@users.noreply.github.com>
Date: Wed, 13 May 2026 17:19:47 -0400
Subject: [PATCH] Enable ServerSideApply for kube-prometheus-stack CRDs in Argo
 CD configuration to avoid last-applied-configuration limit issues during
 deployments.

---
 .../argocd/app-of-apps/kube-prometheus-application.yaml        | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/clusters/noble/bootstrap/argocd/app-of-apps/kube-prometheus-application.yaml b/clusters/noble/bootstrap/argocd/app-of-apps/kube-prometheus-application.yaml
index bb8f5c0..ab70ee3 100644
--- a/clusters/noble/bootstrap/argocd/app-of-apps/kube-prometheus-application.yaml
+++ b/clusters/noble/bootstrap/argocd/app-of-apps/kube-prometheus-application.yaml
@@ -23,6 +23,9 @@ spec:
     server: https://kubernetes.default.svc
     namespace: monitoring
   # Manual sync: Ansible helm runs first; enable automation after cutover (see ../README.md §5).
+  # ServerSideApply: kube-prometheus-stack CRDs exceed the 256KiB **last-applied-configuration** limit
+  # when applied client-side (Argo/kubectl); SSA avoids that annotation.
   syncPolicy:
     syncOptions:
       - CreateNamespace=true
+      - ServerSideApply=true