railiance-enablement/deploy/argocd/railiance01/resources.yaml

# 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}