Skip to content

docs(agents): place the capacity buffer inside the infrastructure layer - #5022

Closed
devantler wants to merge 1 commit into
mainfrom
claude/docs-agents-flux-layers
Closed

devantler wants to merge 1 commit into
mainfrom
claude/docs-agents-flux-layers

Conversation

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

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.

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 devantler left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 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-overprovisioning Flux Kustomization. No Flux Kustomization with that name exists anywhere under k8s/; the top-level ones are infrastructure-controllers, infrastructure, apps and the tenant ones.
  • k8s/providers/hetzner/infrastructure/kustomization.yaml includes overprovisioning/ as an ordinary resource, so the buffer is applied by, and gated with, the infrastructure layer. 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

@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Agentic Engineer

Readiness at 315064431239bb5081de782f911c7981c0d94cdf

  • Tested: CI passed at this head (17 passing, 15 path-skipped, none failing). The change is one sentence of instructions, with no runtime surface to run.
  • Reviewed: fallback self-review GREEN at this head (review 5558999767), posted because CodeRabbit is rate-limited and Codex and Cursor Bugbot are out of usage. No review threads and no other findings.
  • Tried as a reader: read the rendered bullet against the repository: the infrastructure layer's kustomization includes overprovisioning/ and no Flux Kustomization of the removed name exists, so a reader following the instructions now finds the buffer where it really is.

@devantler
devantler marked this pull request as ready for review October 17, 2026 17:29
@devantler
devantler added this pull request to the merge queue Oct 17, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Oct 17, 2026
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Agentic Engineer

Closing as superseded: #4987, merged at 17:35Z, already corrected the same sentence on main (the capacity buffer is part of the Hetzner infrastructure layer, not a separate Flux layer). The queue removed this PR for the resulting merge conflict, and nothing in it is left to land.

@devantler devantler closed this Oct 17, 2026
@devantler
devantler deleted the claude/docs-agents-flux-layers branch October 17, 2026 18:17
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

1 participant