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 server: https://kubernetes.default.svc
namespace: monitoring namespace: monitoring
# Manual sync: Ansible helm runs first; enable automation after cutover (see ../README.md §5). # 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** + # ServerSideApply: avoids oversized **last-applied-configuration** on large chart objects where supported.
# chart **crds.upgradeJob** server-side apply — see values.yaml). # 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: syncPolicy:
syncOptions: syncOptions:
- CreateNamespace=true - CreateNamespace=true

13
clusters/noble/bootstrap/kube-prometheus-stack/values.yaml
View File

@@ -24,14 +24,17 @@ prometheusOperator:
certManager: certManager:
enabled: true enabled: true
# CRDs: Argo CD applies chart CRDs with client-side apply → **last-applied-configuration** can exceed 256KiB. # CRDs + Argo CD: **`helm.skipCrds: true`** on the Argo Application avoids Argo rendering chart CRDs with
# **`crds.upgradeJob`** runs a pre-sync Helm hook that applies CRDs with **`kubectl apply --server-side`**. # **`--include-crds`** (client-side apply would overflow **last-applied-configuration** on huge CRDs).
# Pair with **`helm.skipCrds: true`** on the Argo Application so Argo does not patch those CRDs itself.
# Ref: https://github.com/argoproj/argo-cd/issues/11269 # Ref: https://github.com/argoproj/argo-cd/issues/11269
#
# Do **not** enable **`crds.upgradeJob`** while this release is Argo-managed: the hook creates ConfigMap
# **`kube-prometheus-crds-upgrade`** whose **binaryData** is enormous; Argo client-side apply repeats the same
# annotation size limit on that object. Keep the job **off**; upgrade Prometheus Operator CRDs when you bump
# the chart via **Ansible `helm upgrade`** (or the chart’s manual CRD steps), not via Argo sync.
crds: crds:
upgradeJob: upgradeJob:
enabled: true enabled: false
forceConflicts: true
# --- Longhorn-backed persistence (default chart storage is emptyDir) --- # --- Longhorn-backed persistence (default chart storage is emptyDir) ---
alertmanager: alertmanager: