Skip to content

chore: right-size manager memory back to 512Mi/128Mi #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
1995parham merged 1 commit into from
Jun 20, 2026
Merged

chore: right-size manager memory back to 512Mi/128Mi #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions config/manager/manager.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,14 +50,12 @@ spec:
resources:
limits:
cpu: 500m
# The controllers cache cluster-wide Secrets/ConfigMaps; on a
# cluster with ~33k secrets the cold-start LIST spike exceeded
# 512Mi (and 2Gi), OOMKilling a fresh pod. 4Gi covers the spike.
# TODO: scope the cache (cache.Options.ByObject -> user-argocd)
# so this no longer scales with total cluster secret count.
memory: 4Gi
# Since v0.5.1 the Secret/ConfigMap caches are scoped to
# user-argocd (cache.Options.ByObject), so steady-state usage is
# ~30Mi regardless of cluster size. 512Mi is ample headroom.
memory: 512Mi
requests:
cpu: 100m
memory: 512Mi
memory: 128Mi
serviceAccountName: controller-manager
terminationGracePeriodSeconds: 10