diff --git a/apps/fc-updater/fc-updater.yaml b/apps/fc-updater/fc-updater.yaml
index fd0cf94..c904b2e 100644
--- a/apps/fc-updater/fc-updater.yaml
+++ b/apps/fc-updater/fc-updater.yaml
@@ -24,7 +24,12 @@ spec:
   volumeMode: Filesystem
   resources:
     requests:
-      storage: 10Gi
+      # Sized for fleet bundle storage (LocalFsBundleStore.MaxTotalBytes
+      # soft cap at 25 GiB per project_uc_remaining_4_apps_signed_2026_05_06).
+      # Mike Bundle alone is ~5.1 GiB; cluster live capacity is already
+      # 20 GiB after a manual expand. PVCs cannot shrink, so git must track
+      # at least the live size to avoid the OutOfSync loop.
+      storage: 25Gi
 ---
 apiVersion: apps/v1
 kind: Deployment
diff --git a/apps/monitoring/.argocdignore b/apps/monitoring/.argocdignore
new file mode 100644
index 0000000..e3a3587
--- /dev/null
+++ b/apps/monitoring/.argocdignore
@@ -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