Repository navigation
Conversation
AGENTS.md named an infrastructure-overprovisioning Flux layer that does not exist; the buffer is a folder the Hetzner infrastructure layer includes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — every review lane is unavailable at this head)
Lane state when this was written: CodeRabbit rate-limited (reset about 17:53Z, from its 17:01Z refusal), Codex and Cursor Bugbot out of usage since about 09:55Z. No review artifacts exist on this PR yet. Reviewed at head 315064431239bb5081de782f911c7981c0d94cdf.
What changed: one sentence in the Flux dependency-order bullet of AGENTS.md.
Checks I made:
- The old text named an
infrastructure-overprovisioningFlux Kustomization. No FluxKustomizationwith that name exists anywhere underk8s/; the top-level ones areinfrastructure-controllers,infrastructure,appsand the tenant ones. k8s/providers/hetzner/infrastructure/kustomization.yamlincludesoverprovisioning/as an ordinary resource, so the buffer is applied by, and gated with, theinfrastructurelayer. The new sentence and its path match that.- No other doc in the repository repeats the removed layer name.
Findings: none.
Verdict: GREEN at 3150644
Readiness at
|
Closing as superseded: #4987, merged at 17:35Z, already corrected the same sentence on main (the capacity buffer is part of the Hetzner |
Why
The repository's agent guide names a separate deployment layer for the spare autoscaler capacity that does not exist. Anyone (or any agent) looking for that layer in the cluster finds nothing and may draw wrong conclusions about deploy order.
What
The guide now says where the spare capacity really lives: inside the existing infrastructure layer. Nothing else changes.
No issue: trivial fix.