docs(paperclip): record why the paperclip KS has no monitoring dependsOn edge (REN-86) #985

Merged

Ghost merged 1 commits from atlas/ren-86-paperclip-dependson-monitoring into master 2026-09-25 23:17:56 +00:00

Conversation 2 Commits 1 Files Changed 1

+19

1 Commits

Author	SHA1	Message	Date
atlas-botandClaude Opus 5	1de7071ea9	docs(paperclip): record why this KS has no monitoring edge (REN-86) ... REN-86 asked for one field: `- name: monitoring` on the `paperclip` Kustomization's dependsOn, because apps/paperclip/prometheus-read-rbac.yaml (PR #984) puts a Role and a RoleBinding in namespace `monitoring` and a from-scratch bootstrap was expected to fail applying them. The premise does not hold, so the field is not added and the reasoning is written down instead: - Namespace `monitoring` is not created by the `monitoring` Kustomization. It is declared in kubernetes/infrastructure/namespaces/namespaces.yaml, applied by `infrastructure`, which this Kustomization already dependsOn. - `infrastructure` runs wait: false, so it applies the namespaces on its first pass and only its healthChecks gate readiness. It cannot report Ready before the namespace exists, and this Kustomization cannot start before that. - Role and RoleBinding are core rbac.authorization.k8s.io/v1 kinds, and a RoleBinding may reference a Role that does not exist yet. Nothing on this path needs a kube-prometheus-stack CRD or workload, so there is no analogue of the monitoring-rules/PrometheusRule split. Adding the edge would also couple the Kustomization that carries the paperclip pod to `monitoring` readiness, which itself waits on grafana-db, kube-prometheus-stack, Loki, Alloy and blackbox-exporter for up to 30m. Comments only: the parsed manifest is identical to master. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-25 23:09:27 +00:00