Argo CD Security FAQs: RBAC, SSO, Projects (2027)
46 Argo CD security and multi-tenancy FAQs: AppProjects, argocd-rbac-cm, v3 RBAC changes, SSO, tokens, apps in any namespace, GPG checks.
Argo CD security FAQs in DevOps interviews cover how one Argo CD instance safely serves many teams: AppProjects that limit repos, clusters and resource kinds, RBAC in argocd-rbac-cm, SSO through Dex or OIDC, local accounts and project tokens, Applications in any namespace, and locking down the admin account. This page answers 46 of those questions.
The answers were checked against the Argo CD stable documentation in November 2026, when the latest release was v3.6.1. For general Argo CD questions, use our main scenario-based Argo CD interview questions and the 70+ Argo CD interview questions. This page stays on security and multi-tenancy, which those lists only touch.
Key takeaways
- The
defaultproject allows any repo, any cluster and any resource. Lock it down or stop using it in shared instances. - RBAC lives in the
argocd-rbac-cmConfigMap as Casbin-stylepandglines. A matching deny beats any allow. - Since v3.0,
updateanddeleteon an Application no longer apply to its sub-resources unless you grant them explicitly. - Prefer SSO over local users. Disable the built-in admin with
admin.enabled: "false"once SSO works. - Applications in any namespace need both the
--application-namespacessetting and a matchingsourceNamespacesentry in the project.
Where each control lives
| Control | Where you configure it |
|---|---|
| Global RBAC | argocd-rbac-cm (policy.csv, policy.default, scopes) |
| Local users, admin, SSO | argocd-cm (accounts.*, admin.enabled, dex.config, oidc.config) |
| Team boundaries | AppProject (sourceRepos, destinations, resource allow and deny lists, roles) |
| Apps outside argocd namespace | argocd-cmd-params-cm application.namespaces plus project sourceNamespaces |
| Login throttling | ARGOCD_SESSION_FAILURE_MAX_FAIL_COUNT and related variables |
FAQs for freshers
1. What is an AppProject?
A custom resource that groups Applications and limits what they can do: which Git or Helm sources they use, which clusters and namespaces they deploy to, and which Kubernetes kinds they may create.
2. What is the default project?
A project created automatically. Applications without a project use it. It allows deployments from any source repo, to any cluster, with all resource kinds.
3. Why is the default project a risk?
Anyone who can create an Application in it can deploy anything anywhere. In a shared instance, create one project per team and restrict or empty the default project.
4. Where is Argo CD RBAC configured?
In the argocd-rbac-cm ConfigMap, usually in the argocd namespace, plus roles defined inside each AppProject.
5. What are the built-in roles?
role:readonly (read everything) and role:admin (full access).
6. What does a policy line look like?
p, subject, resource, action, object, effect. A g line assigns a user or group to a role.
p, role:team-a-dev, applications, sync, team-a/*, allow
p, role:team-a-dev, applications, get, team-a/*, allow
g, my-org:team-a, role:team-a-dev
7. Which RBAC resources exist?
applications, applicationsets, clusters, projects, repositories, write-repositories, accounts, certificates, gpgkeys, logs, exec and extensions.
8. What is policy.default?
The role every authenticated user gets, for example role:readonly. A deny rule cannot block it, so the docs advise keeping it minimal.
9. What is SSO in Argo CD?
Logging in through an identity provider instead of local passwords, either through the bundled Dex or directly with an existing OIDC provider.
10. How do you get the initial admin password?
It is stored in the argocd-initial-admin-secret Secret. Change it and delete the secret after first login, or disable admin once SSO works.
11. What is a local account?
A user defined in argocd-cm as accounts.NAME with capabilities apiKey, login or both. Local users have no groups or login history.
12. What is argocd account can-i?
A CLI command that checks whether the current user can perform an action, for example argocd account can-i sync applications 'team-a/*'.
FAQs for 2 to 5 years of experience
13. How do you restrict a project to certain repos?
List them in spec.sourceRepos. Globs are supported, and a leading ! denies a pattern.
apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
name: team-a
namespace: argocd
spec:
sourceRepos:
- https://github.com/example/team-a-*
destinations:
- server: https://kubernetes.default.svc
namespace: team-a-*
clusterResourceWhitelist: []
namespaceResourceBlacklist:
- group: ''
kind: ResourceQuota
14. How do you stop a team creating cluster-scoped resources?
Leave clusterResourceWhitelist empty, or allow only specific kinds. You can also allow a kind by name pattern, for example only Namespaces starting with team1-.
15. What do namespaceResourceBlacklist and Whitelist do?
They deny or allow namespaced kinds. Use them to stop teams creating objects such as ResourceQuota or NetworkPolicy that the platform team owns.
16. What are project roles?
Roles defined inside an AppProject with their own policies and groups. They can issue JWT tokens scoped to that project, for CI systems.
argocd proj role create team-a ci
argocd proj role add-policy team-a ci -a sync -o '*' -p allow
argocd proj role create-token team-a ci -e 24h
17. Why prefer short token lifetimes?
Project tokens are not stored by Argo CD, and a token without expiry stays valid until you delete it. The docs recommend short-lived tokens rotated from CI.
18. What is Dex Token Exchange?
A way for CI platforms that issue OIDC tokens, such as GitHub Actions or GitLab CI, to exchange their own identity token for Argo CD access, so no long-lived Argo CD token sits in the pipeline.
19. What does scopes do in RBAC config?
It lists the OIDC claims Argo CD reads for group membership. The default is [groups]. Add email if you write policies by email.
20. What changed for RBAC in v3.0?
update and delete on an Application now apply only to the Application. To let a user delete a Pod inside it you need a sub-resource rule such as delete/*/Pod/*/*. Setting server.rbac.disableApplicationFineGrainedRBACInheritance to false restores the old behaviour.
21. How do you control access to pod logs and exec?
Through the logs resource with action get and the exec resource with action create. Grant exec rarely, because it is a shell in a running pod.
22. How do you validate RBAC before applying it?
argocd admin settings rbac validate checks the policy, and argocd admin settings rbac can tests a subject against an action, using a local file or the live config.
23. What is policy.matchMode?
It sets how object patterns match: glob (default) or regex.
24. How do you disable the admin account?
Set admin.enabled: "false" in argocd-cm after confirming SSO admins can log in.
25. How does Argo CD slow password guessing?
It throttles failed logins. ARGOCD_SESSION_FAILURE_MAX_FAIL_COUNT sets how many failures are allowed before rejecting attempts; the default is 5.
26. How do you enable Applications in team namespaces?
Set application.namespaces in argocd-cmd-params-cm (or the --application-namespaces flag on server and controller), and list the namespace in the project's spec.sourceNamespaces.
27. Why is apps-in-any-namespace useful for multi-tenancy?
Teams can manage Application objects with plain Kubernetes RBAC in their own namespace, without write access to the argocd namespace.
28. How do repository credentials stay separate per team?
Repository Secrets can be scoped to a project, so only that project's Applications use them. Grant the repositories resource only to admins.
FAQs for senior engineers
29. One shared Argo CD or one per team?
Shared is cheaper and gives one view, but needs strict projects and RBAC. Separate instances isolate failures and credentials. Many companies run one per environment or business unit.
30. Why are cluster credentials sensitive?
Argo CD stores credentials for every managed cluster as Secrets, often with broad rights. Anyone who can read them can act on those clusters, so restrict access to the argocd namespace tightly.
31. How do you limit what Argo CD itself can do on a cluster?
Register clusters with a service account that has only the rights the projects need, and consider project destinationServiceAccounts to make syncs impersonate a narrower identity. Sync impersonation is a beta feature (beta since v3.5.0) and is disabled by default, so test it before relying on it.
32. How do you verify that deployed commits are trusted?
Enable GPG signature verification: import public keys and list allowed key IDs in the project's signatureKeys. Argo CD then refuses to sync unsigned or wrongly signed commits.
33. How do you protect production from accidental syncs?
Sync windows on the production project, manual sync only, and RBAC that grants sync on prod apps to a small group.
34. How do you audit who changed what?
Git history shows the desired state change. Argo CD records sync operations with the user, and Kubernetes audit logs show API calls. Send all three to your log platform.
35. How should CI authenticate in 2027?
Prefer Dex Token Exchange or client credentials with an OIDC provider. The docs call the password grant deprecated in OAuth 2.1 and warn it bypasses MFA.
36. What does argocd login --core do?
It skips Argo CD authentication and talks to the Kubernetes API directly with your kubeconfig. Access then depends entirely on Kubernetes RBAC.
37. How do you handle Helm or Git secrets in manifests?
Never commit plain secrets. Use Sealed Secrets, SOPS or an external secrets operator. See tools to manage Kubernetes secrets safely.
38. How do you harden the Argo CD install itself?
Keep it on a supported minor version, enable TLS end to end, restrict network access to the API server, and follow the security advisories in the GitHub repository. v3.3 reached end of life on 3 November 2026.
Scenario FAQs
39. Scenario: team A deployed into team B's namespace.
Their project's destinations was too broad. Narrow it to team-a-* namespaces and check the default project is not used.
40. Scenario: after upgrading to v3, developers cannot delete stuck pods from the UI.
The v3 fine-grained change. Add delete/*/Pod/*/* rules for those apps rather than restoring inheritance globally.
41. Scenario: an SSO user sees nothing.
Their groups claim is not arriving or does not match a g line. Check the token claims and the scopes setting.
42. Scenario: a CI token leaked.
Delete the token with argocd proj role delete-token, issue a short-lived one, and move CI to token exchange.
43. Scenario: an Application in a team namespace is ignored.
The namespace is missing from application.namespaces or from the project's sourceNamespaces.
44. Scenario: a developer created a ClusterRole through Argo CD.
The project allowed cluster-scoped kinds. Empty clusterResourceWhitelist and review what was created.
45. Scenario: someone keeps logging in as admin.
Disable admin, rotate its password first, and give named SSO users the admin role instead.
46. Scenario: auditors ask for proof that only reviewed code reaches production.
Show branch protection in Git, GPG signature verification in the prod project, and sync logs.
GitOps background is in what is GitOps and GitOps principles and Argo CD interview questions. For experienced-level operations, see Argo CD questions for experienced engineers. Kubernetes RBAC basics are part of our CKA training in Pune, in Kharadi or live online.
FAQ
Where is Argo CD RBAC configured?
In the argocd-rbac-cm ConfigMap, plus roles inside each AppProject.
Is the default project safe to use?
Not in a shared instance. It allows any repo, cluster and resource kind.
What changed in Argo CD 3.0 RBAC?
Update and delete on an Application no longer cover its sub-resources unless granted explicitly.
How do I disable the admin user?
Set admin.enabled to "false" in argocd-cm after SSO works.
How should CI log in to Argo CD?
With short-lived project tokens or Dex Token Exchange, not stored admin passwords.
What is the latest Argo CD version?
v3.6.1 was the latest release in early November 2026.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0