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

RAIL-EN-WP-0003-T01: prepare wave-2 Argo CD requests
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
application-controller 30m/432Mi, repo-server 10m CPU; limits unchanged.
Server-side diff against live: resource requests only. No apply.

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:
tegwick 2026-10-22 00:06:46 +02:00
parent 25ba8eef42
commit 894bc084e3
2 changed files with 13 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
deploy/argocd/railiance01/resources.yaml
View file

@ -15,7 +15,7 @@ spec:
containers:
- name: argocd-application-controller
resources:
requests: {cpu: 50m, memory: 256Mi}
requests: {cpu: 30m, memory: 432Mi}
limits: {cpu: 1000m, memory: 1Gi}
---
apiVersion: apps/v1
@ -33,7 +33,7 @@ spec:
containers:
- name: argocd-repo-server
resources:
requests: {cpu: 25m, memory: 128Mi}
requests: {cpu: 10m, memory: 128Mi}
limits: {cpu: 1000m, memory: 1Gi}
---
apiVersion: apps/v1

11
workplans/RAIL-EN-WP-0003-wave2-resource-right-sizing.md
View file

@ -55,6 +55,17 @@ Steps:
Verification: `kubectl -n <ns> get pod -o jsonpath='{..resources}'` shows the new requests; pods Ready with no new restarts or OOMKilled over 24h; for CPU decreases the throttle ratio and request latency stay at or below the 7d baseline; node request total drops by the expected delta.
Prepared 2026-10-22 (wave-2 worker W3; no apply, cluster read-only): source
`deploy/argocd/railiance01/resources.yaml` (kustomize over the pinned core
install). application-controller requests 50m/256Mi -> 30m/432Mi, repo-server
25m/128Mi -> 10m/128Mi; limits unchanged. Full `kubectl kustomize` render,
server-side `kubectl diff -n argocd` against live: only these two objects,
`containers[].resources.requests` keys; no other drift. Apply (local kubectl,
per README "Apply the declared state"):
`make argocd-fetch && kubectl kustomize deploy/argocd/railiance01 | kubectl apply --server-side -n argocd -f -`.
Restarts the application-controller StatefulSet pod and the repo-server pod
(Argo reconciliation pauses briefly; no ingress impact).
Rollback: revert the source commit and re-sync/re-apply; the before values in the table above are the rollback target. Keep before/after `kubectl get -o yaml` captures as the receipt.
ArgoCD manages itself: apply through the RAIL-EN-WP-0002 declared-state path and confirm all Applications return to Synced/Healthy afterwards.