stack.basicstack.de

basicstack/stack.basicstack.de

Fork 0

Commit graph

Author	SHA1	Message	Date
CTO Agent	43610fb16d	feat(argocd): switch to community Helm chart (DEV-519) Replace the vendored ~33k-line apps/argocd/argocd-install.yaml with the argoproj/argo-helm chart argo-cd 10.4.0 (app v3.5.1). Values live in apps/argocd/values.yaml; the local kustomize wrapper now only carries the Traefik ingress and the sealed secrets. The root apps/app-argocd.yaml Application becomes multi-source (chart + this repo as $values), enables ServerSideApply + ApplyOutOfSyncOnly, and pins the resources-finalizer explicitly. Behavior-equivalent to the previous install: same URL, OIDC (Pocket ID), argo_admins RBAC mapping, resource.exclusions list, and per-component memory limits (DEV-281). Ingress is disabled in the chart; ours stays in kustomize with cert-manager letsencrypt-prod annotations. README.md updated with the Helm bump procedure. argocd-install.yaml removed. Verified locally: helm template argocd argo/argo-cd --version 10.4.0 \ -f apps/argocd/values.yaml -n argocd # renders 34k lines, image: quay.io/argoproj/argocd:v3.5.1 kustomize build apps/argocd/ # renders 1 Ingress + 3 SealedSecrets, no errors Refs: DEV-521, plan DEV-519 §3, §8. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-08-23 08:32:23 +00:00
CTO Agent	b874f3d184	Add memory limits to Argo CD components to prevent OOM incidents Implements resource governance for all Argo CD components via kustomization overlay. This prevents unlimited memory consumption that led to the control plane resource exhaustion incident (DEV-281). Resource limits applied: - application-controller: 512Mi limit, 256Mi request - repo-server: 512Mi limit, 256Mi request - redis: 256Mi limit, 128Mi request - server: 256Mi limit, 128Mi request - notifications-controller: 128Mi limit, 64Mi request - applicationset-controller: 256Mi limit, 128Mi request The limits are based on observed usage patterns with headroom for growth while preventing runaway memory consumption. Usage: kubectl apply -k apps/argocd/ Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-07-12 09:19:28 +00:00

Author

SHA1

Message

Date

CTO Agent

43610fb16d

feat(argocd): switch to community Helm chart (DEV-519)

Replace the vendored ~33k-line apps/argocd/argocd-install.yaml with the
argoproj/argo-helm chart argo-cd 10.4.0 (app v3.5.1). Values live in
apps/argocd/values.yaml; the local kustomize wrapper now only carries the
Traefik ingress and the sealed secrets. The root apps/app-argocd.yaml
Application becomes multi-source (chart + this repo as $values), enables
ServerSideApply + ApplyOutOfSyncOnly, and pins the resources-finalizer
explicitly.

Behavior-equivalent to the previous install: same URL, OIDC (Pocket ID),
argo_admins RBAC mapping, resource.exclusions list, and per-component
memory limits (DEV-281). Ingress is disabled in the chart; ours stays in
kustomize with cert-manager letsencrypt-prod annotations.

README.md updated with the Helm bump procedure. argocd-install.yaml
removed.

Verified locally:
  helm template argocd argo/argo-cd --version 10.4.0 \
    -f apps/argocd/values.yaml -n argocd
  # renders 34k lines, image: quay.io/argoproj/argocd:v3.5.1
  kustomize build apps/argocd/
  # renders 1 Ingress + 3 SealedSecrets, no errors

Refs: DEV-521, plan DEV-519 §3, §8.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-08-23 08:32:23 +00:00

CTO Agent

b874f3d184

Add memory limits to Argo CD components to prevent OOM incidents

Implements resource governance for all Argo CD components via kustomization
overlay. This prevents unlimited memory consumption that led to the control
plane resource exhaustion incident (DEV-281).

Resource limits applied:
- application-controller: 512Mi limit, 256Mi request
- repo-server: 512Mi limit, 256Mi request
- redis: 256Mi limit, 128Mi request
- server: 256Mi limit, 128Mi request
- notifications-controller: 128Mi limit, 64Mi request
- applicationset-controller: 256Mi limit, 128Mi request

The limits are based on observed usage patterns with headroom for growth
while preventing runaway memory consumption.

Usage: kubectl apply -k apps/argocd/

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-07-12 09:19:28 +00:00

2 commits