f75b51c02d
Creates the Argo CD Application that manages all cluster infrastructure applications from the stack.basicstack.de repository. Configuration: - Points to cluster-internal Forgejo (forgejo.forgejo.svc.cluster.local) - Excludes argocd directory to prevent self-management - Enables selfHeal for automatic sync of changes - Disables prune for manual deletion approval - Deployed to the cluster and verified working All existing services (Stalwart, Directus, Forgejo, BookStack, Pocket ID, OpenCloud, Passbolt) remain operational. Some pods restarted due to applying pending git changes (expected GitOps behavior). Note: Warning about duplicate opencloud namespace definition in openldap-deployment.yaml and opencloud-deployment.yaml - does not affect functionality, can be addressed in follow-up cleanup. Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| app-stack-basicstack-de.yaml | ||
| argocd-ingress.yaml | ||
| argocd-install.yaml | ||
| argocd-oidc-secret-sealed.yaml | ||
| kustomization.yaml | ||
| README.md | ||
| repo-basicstack-org-secret-sealed.yaml | ||
| repo-stack-basicstack-de-secret-sealed.yaml | ||
Argo CD Deployment
This directory contains the Argo CD deployment configuration for the basicstack.de k3s cluster.
Files
argocd-install.yaml- Auto-generated Argo CD installation manifest (DO NOT EDIT DIRECTLY)kustomization.yaml- Kustomize overlay that adds resource limits and other customizationsargocd-ingress.yaml- Ingress configuration for Argo CD UIargocd-oidc-secret-sealed.yaml- Sealed secret for OIDC integrationrepo-*.yaml- Sealed secrets for Git repository access
Resource Limits
IMPORTANT: Resource limits were added after DEV-281 (resource exhaustion incident on 2026-07-12).
All Argo CD components now have memory limits to prevent OOM incidents:
| Component | Memory Limit | Memory Request |
|---|---|---|
| application-controller | 512Mi | 256Mi |
| repo-server | 512Mi | 256Mi |
| redis | 256Mi | 128Mi |
| server | 256Mi | 128Mi |
| notifications-controller | 128Mi | 64Mi |
| applicationset-controller | 256Mi | 128Mi |
These limits are based on observed usage patterns and provide headroom while preventing unlimited memory consumption.
Deployment
Option 1: Apply with kustomize (RECOMMENDED)
kubectl apply -k apps/argocd/
This will apply the base manifests plus all patches defined in kustomization.yaml.
Option 2: Direct apply (not recommended)
kubectl apply -f apps/argocd/argocd-install.yaml
kubectl apply -f apps/argocd/argocd-ingress.yaml
# etc.
Note: This skips the resource limit patches and is NOT recommended.
Updating Argo CD
When updating to a new Argo CD version:
-
Download the new install manifest:
curl -sSL https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml > argocd-install.yaml -
Apply with kustomize (resource limits will be automatically applied):
kubectl apply -k apps/argocd/ -
Verify resource limits are in place:
kubectl get statefulset,deployment -n argocd -o custom-columns='NAME:.metadata.name,MEMORY_LIMIT:.spec.template.spec.containers[0].resources.limits.memory'
Troubleshooting
Check resource usage
kubectl top pods -n argocd
Check if resource limits are applied
kubectl get deployment,statefulset -n argocd -o json | jq '.items[] | {name: .metadata.name, limits: .spec.template.spec.containers[0].resources.limits}'
Rollback if needed
If there are issues after applying resource limits:
# Remove limits from a specific component
kubectl patch deployment -n argocd argocd-server --type='json' -p='[{"op": "remove", "path": "/spec/template/spec/containers/0/resources"}]'
History
- 2026-07-12: Added resource limits via kustomization to prevent OOM incidents (DEV-281)
- 2026-07-11: Initial deployment