Repository navigation
docs(governance): amend capacity limit l3 to three economical nodes - #51
Merged
Merged
Conversation
Records the maintainer's 2026-09-14 decision to run the economical cluster on three bootstrap nodes: two could not hold the reactivated platform, and the quota still fits with both profiles up. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Capacity limit L3 in
docs/Governance and IaC standards program.md§11 movesthe economical cluster from two bootstrap nodes to three. The D2 row strikes
"two" and points to a new subsection, "Amendment of L3 by the maintainer,
2026-09-14", which records why, the quota arithmetic, and the cost. D2's
earlier amendment is recorded the same way.
Why
The maintainer took the decision on 2026-09-14, for two reasons:
lex-mts-eco-eks-mainwas reactivated, the pods' CPU requests filled 93% and 99% of the two nodes.
eco.microtodosuite.onlineneeds the AWS Load Balancer Controller's tworeplicas.
A limit decision is changed by a recorded amendment, not in conversation.
Tasks
microservice-app-ai-agents specs/001-governance-and-iac-program T028 (the
capacity limits, already ticked). No task tracks an amendment of a decided
limit; this pull request is its record, and the operator's
eco.tfvarscarries the new value.
The task register is updated in this pull request — N/A: no task changes state
Every task ticked here was verified by locating its artifact — none is ticked
How it is verified
Read-only, on 2026-09-14:
Quotas.
aws service-quotas get-service-quotareturns 16 forL-1216C47A(Running On-Demand Standard instances) and 32 for
L-34B43A08(StandardSpot Instance Requests).
Current use.
describe-instancesshows five runningm7i-flex.largeinstances, 10 vCPU: two
ecoand one per full cluster.Node groups.
ecois at 2/2/4. Each full group is at 1/1/2.The arithmetic in the amendment:
econode brings the account to 12 of 16The change itself. The saved plan for
eco/workloadholds exactly onein-place update of the node group's
scaling_config, from 2/2/4 to 3/3/4.Infrastructure changes: the documentation consulted through the required MCP servers is listed above — N/A: documentation only
Risk and rollback
Documentation only. Returning to two nodes is a new amendment and a plan with
desired_size = 2.What this PR does not do
It changes neither the full clusters' L3 (one bootstrap node each) nor L4.
🤖 Generated with Claude Code