jakman85andClaude Opus 4.8
eeb97208fa
Enabling monitoring deadlocked the platform Kustomization: alerts.yaml ships PrometheusRule CRs whose monitoring.coreos.com CRDs are installed by the kube-prometheus-stack HelmRelease in the SAME pass → 'no matches for kind PrometheusRule' → atomic apply failure → NO monitoring HelmReleases created. Same controllers/configs fix as cert-manager/kyverno: drop alerts.yaml from platform/monitoring and apply it via platform-config (dependsOn platform), so the monitoring CRDs exist first. Verified: platform has 0 PrometheusRule (keeps the 3 monitoring HRs); platform-config has the 8 alert rules; gate PASS. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
15 lines
527 B
YAML
15 lines
527 B
YAML
---
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- namespace.yaml
|
|
- helmrepositories.yaml
|
|
- kube-prometheus-stack.yaml
|
|
- loki.yaml
|
|
- alloy.yaml
|
|
# NOTE: alerts.yaml (PrometheusRule CRs) needs the monitoring.coreos.com CRDs that the
|
|
# kube-prometheus-stack HelmRelease above installs → applied by the platform-config Kustomization
|
|
# (dependsOn platform) so the CRDs exist first. File stays here for locality.
|
|
- grafana-admin-credentials.sops.yaml
|
|
- alertmanager-smtp.sops.yaml
|