Declare Argo CD Core v3.5.3 on railiance01 and its resource bounds
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Has been cancelled

Pinned core-install.yaml (sha256 1a87025d...c448) with a kustomize
resources patch for the four workloads. The unpatched pin diffs clean
against live; the resources patch is declared only, and its apply waits
on the founder in RAIL-EN-WP-0002-T02. SCOPE.md no longer says ArgoCD is
absent from railiance01.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 18:41:24 +02:00
parent f91a5298cb
commit 70295b6b2b
8 changed files with 284 additions and 13 deletions

View file

@ -0,0 +1,68 @@
# Requests and limits for the four Argo CD Core workloads. Upstream core sets
# none, so the live pods are BestEffort. Idle use on 2026-09-21 (kubectl top,
# 0 Applications): controller 2m/23Mi, applicationset 1m/19Mi,
# repo-server 1m/19Mi, redis 5m/4Mi. Requests sit above idle to leave room for
# phase B adoption; memory limits bound the pods; CPU limits are generous.
# Total added requests: 95m CPU, 480Mi memory (init containers do not add).
# NOT YET APPLIED: see RAIL-EN-WP-0002-T02.
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: argocd-application-controller
spec:
template:
spec:
containers:
- name: argocd-application-controller
resources:
requests: {cpu: 50m, memory: 256Mi}
limits: {cpu: 1000m, memory: 1Gi}
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-repo-server
spec:
template:
spec:
initContainers:
- name: copyutil
resources:
requests: {cpu: 10m, memory: 32Mi}
limits: {cpu: 100m, memory: 64Mi}
containers:
- name: argocd-repo-server
resources:
requests: {cpu: 25m, memory: 128Mi}
limits: {cpu: 1000m, memory: 1Gi}
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-applicationset-controller
spec:
template:
spec:
containers:
- name: argocd-applicationset-controller
resources:
requests: {cpu: 10m, memory: 64Mi}
limits: {cpu: 250m, memory: 256Mi}
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-redis
spec:
template:
spec:
initContainers:
- name: secret-init
resources:
requests: {cpu: 10m, memory: 32Mi}
limits: {cpu: 100m, memory: 64Mi}
containers:
- name: redis
resources:
requests: {cpu: 10m, memory: 32Mi}
limits: {cpu: 200m, memory: 128Mi}