gsdavidp/home-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine Argo CD configuration for kube-prometheus-stack to clarify CRD management and server-side apply limitations, ensuring compatibility and preventing last-applied-configuration overflow during deployments.

Browse Source
This commit is contained in:
Nikholas Pcenicni
2026-05-13 17:29:09 -04:00
parent b26099342c
commit a9d6cbb6c5
2 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
clusters/noble/bootstrap/argocd/app-of-apps/kube-prometheus-application.yaml
View File

@@ -24,8 +24,9 @@ spec:
server: https://kubernetes.default.svc
namespace: monitoring
# Manual sync: Ansible helm runs first; enable automation after cutover (see ../README.md §5).
# ServerSideApply: helps large manifests Argo applies directly (CRDs are handled via **helm.skipCrds** +
# chart **crds.upgradeJob** server-side apply — see values.yaml).
# ServerSideApply: avoids oversized **last-applied-configuration** on large chart objects where supported.
# CRDs: **helm.skipCrds** (Argo must not `--include-crds`). Do not enable chart **crds.upgradeJob** under Argo —
# its hook ConfigMap exceeds the same annotation limit; CRD bumps via Ansible **helm upgrade** (see values.yaml).
syncPolicy:
syncOptions:
- CreateNamespace=true