bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

fix(infra): unstick fc-updater + monitoring ArgoCD apps

Browse Source 
fc-updater PVC: bump updatecenter-data storage 10Gi → 25Gi.
The cluster PVC was already manually expanded to 20Gi to fit Mike Bundle
(~5.1 GiB) plus the LocalFsBundleStore.MaxTotalBytes soft cap of 25 GiB
(see project_uc_remaining_4_apps_signed_2026_05_06). PVCs cannot shrink,
so ArgoCD couldn't sync the smaller git value (OutOfSync, retried 5x with
"field can not be less than status.capacity"). Setting git to 25Gi gives
headroom matching the soft cap.

monitoring .argocdignore: skip bare dashboard JSON files.
Both fc-updatecenter-dashboard.json and flowercore-remotedesktop-grafana-
dashboard.json live in apps/monitoring/ as source-of-truth for file-
provisioning to noc1's /opt/monitoring/grafana/dashboards/. ArgoCD's
manifest parser tries to unmarshal every file and chokes on bare dashboard
JSON ("Object 'Kind' is missing"), which then poisoned the whole
infra-monitoring Application status (Unknown sync, no comparison possible).
The .argocdignore tells ArgoCD to skip *.json — actual K8s deploys happen
via ConfigMap wrappers like grafana-dashboard-remotedesktop.yaml.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Codex
2026-05-07 10:11:20 -05:00
parent c4065b15a3
commit df22774674
2 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
apps/monitoring/.argocdignore Normal file
View File

@@ -0,0 +1,15 @@
# Bare Grafana dashboard JSON files are kept here as a CONVENIENCE source
# for the file-provisioning path on noc1 (per
# feedback_grafana_dashboard_shape_depends_on_noc1_delivery_path and
# feedback_monitoring_k8s_target_vs_live_podman). They are NOT K8s
# manifests — they have no `apiVersion` / `kind` / `metadata`. ArgoCD's
# kubernetesIngress provider tries to unmarshal every file in the
# directory and chokes on raw dashboard JSON with "Object 'Kind' is
# missing", which then poisons manifest generation for the whole
# infra-monitoring Application.
#
# When a dashboard needs to be K8s-deployed (i.e. file-provisioned via
# Grafana sidecar in noc-monitoring.yaml), wrap the JSON in a ConfigMap
# YAML next to it (see grafana-dashboard-remotedesktop.yaml as the
# canonical pattern).
*.json