Skip to content

Conversation

@cjcocokrisp
Copy link
Contributor

@cjcocokrisp cjcocokrisp commented Feb 11, 2026

Closes: #24833

The linked above issue describes that if a namespace is specified in the destination of an application's spec and that namespace does not exist, cluster scoped RBAC resources will fail to apply.

This is due to the auth reconcile operation that is performed doing a namespace check before hand due to a side effect where it creates namespaces that do not exist. This fix adds a check to see if the kind of the RBAC object is a ClusterRole or ClusterRoleBinding then skips the namespace check if it is.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • [N/A] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • [N/A] Does this PR require documentation updates?
  • [N/A] I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • [N/A] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • [N/A] My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@cjcocokrisp cjcocokrisp requested a review from a team as a code owner February 11, 2026 14:48
@bunnyshell
Copy link

bunnyshell bot commented Feb 11, 2026

✅ Preview Environment deployed on Bunnyshell

Component Endpoints
argocd https://argocd-qsgzby.bunnyenv.com/
argocd-ttyd https://argocd-web-cli-qsgzby.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔴 /bns:stop to stop the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@cjcocokrisp cjcocokrisp force-pushed the fix/namespace-must-exist-to-sync-cluster-scoped-rbac-objects branch from 1ce6d76 to dd6b981 Compare February 11, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ArgoCD wants namespace to exist for non-namespaced RBAC objects

1 participant