coulomb/railiance-cluster
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wave-2 right-sizing applied 2026-10-22 (CUST-WP-0071)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
This commit is contained in:
codex 2026-10-22 01:05:00 +02:00
parent d775ba8fa7
commit 0e8df471c7
2 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
WORK-RECORDS.md
View file

@ -77,5 +77,5 @@
| task | RCLUSTER-WP-0019-T03 | done | — | workplans/RCLUSTER-WP-0019-k3s-admin-kubeconfig-mode.md |
| task | RCLUSTER-WP-0020-T01 | done | — | workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md |
| task | RCLUSTER-WP-0020-T02 | done | — | workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md |
| task | RCLUSTER-WP-0020-T03 | todo | — | workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md |
| task | RCLUSTER-WP-0020-T03 | wait | — | workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md |
| task | RCLUSTER-WP-0020-T04 | todo | — | workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md |

8
workplans/RCLUSTER-WP-0020-node-budget-knative-caps-and-wave2-allocation.md
View file

@ -59,7 +59,9 @@ state_hub_task_id: "c9a0edd8-c8a4-5a5e-b360-05e7ffda3010"
```task
id: RCLUSTER-WP-0020-T03
status: todo
status: wait
needs_human: true
blocking_reason: "k3s addons (coredns, metrics-server, local-path-provisioner) are founder-run with sudo on railiance01; cert-manager and traefik applied."
priority: medium
state_hub_task_id: "5ce03eaf-a279-59ba-96b4-3bd2ca13dbad"
```
@ -139,3 +141,7 @@ certificate object by the ValidatingAdmissionPolicy `reject-secret-last-applied`
runtime. Choose one: leave it out of the render after the first install, or apply
it server-side. Also make `install.sh` reach the cluster without the failing
ssh + k3s.yaml hop, since the remote user cannot read the k3s kubeconfig.
## Applied — 2026-10-22 (RCLUSTER-WP-0020-T03)
Partial: cert-manager (Helm revision 2; the ACME solver flag is now written into values, founder-approved) and traefik (HelmChartConfig; ingress unaffected) are applied. coredns, metrics-server and local-path-provisioner are k3s addons. They are founder-run on railiance01 (`sudo python3 install/k3s-addons/wave2-requests.py`, then `--apply`), because the agent cannot read the k3s manifests directory or use sudo. kube-reserved/system-reserved come only after that and a measurement. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.