fix(galactic): finish Turin PodCIDR migration - #14362
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 774608bac3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 729ff49242
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Status on 2026-09-07 UTC: Turin has re-registered with `10.244.0.0/23`; Altra retains `10.244.5.0/24`. | ||
| The template now raises only Turin to 500 pods. Apply that cap after its storage recovery; Altra remains at 250. |
There was a problem hiding this comment.
Update the remaining runbook steps for migrated Turin
After these lines mark Turin as migrated to /23 with a durable 500-pod cap, the same runbook still describes Turin as /24/250 at lines 9-22, directs every target to run the non-migrated preflight at line 124, and claims the durable template still caps the node at 250 at line 189. podcidr_preflight.py:63-69 makes that command expect exactly 250 pods unless --migrated is supplied, so following the documented Turin path after this change produces a failing gate and misleading restoration steps. The Omni README was corrected, but this operational runbook also needs target-aware/current instructions.
AGENTS.md reference: AGENTS.md:L57-L58
Useful? React with 👍 / 👎.
Summary
/23PodCIDR by raising its durable kubelet cap to 500. Keep Altra at 250 until its own migration.ip link. Physical NICs exposing VEB mode are not CNI bridge ports.Related Issues
None
Testing
bun test devices/galactic/omni/render-template.test.ts: 7 tests passed.git diff --check: passed.maxPods: 250to500.10.244.0.0/23with a new Node UID and the original host boot ID and etcd member ID. Exact-plan cleanup completed; both CNI links and seven obsolete lease records were archived/removed as intended.Breaking Changes
None. Altra's live
/24remains capped at 250.Checklist