New Service Deployment

Decision tree

New service?
├─ Official Helm chart exists (Harbor, DefectDojo, Jenkins, Kong, …)?
│  └─ Path A: Helm + dual-source Argo CD → argocd/app-list.yaml
└─ Simple app / no suitable chart / custom Deployment?
   └─ Path B: Kustomize + single-source Argo CD → argocd/app-list.yaml

Ingress / cluster-wide static config?
└─ Always Path C: static/ (Argo app static-manifest already syncs it)

Secrets (passwords, tokens)?
└─ Kustomize only: <service>/secret.yaml (gitignored), name file secret.yaml

Do not create a separate “helmlist” file — all Applications live in argocd/app-list.yaml. The root app-of-apps Application watches that file only.