Skip to content

Conversation

@ATGardner
Copy link
Contributor

What

replace CluterRoleBinding to a non-existing ClusterRole argo-server with RoleBinding to the existing Role.

Why

this CRB was a leftover since moving argo-workflows to namespced-mode

Notes

Ensure the RoleBinding kind is explicitly set to "RoleBinding"
and the role is set to "Role" for the app-proxy Argo workflows.
This change improves clarity and consistency in the RBAC configuration.
@ATGardner ATGardner self-assigned this Dec 17, 2025
@github-actions github-actions bot added the stable pr into a stable release branch label Dec 17, 2025
@ATGardner ATGardner changed the base branch from stable/0.26 to main December 17, 2025 08:15
@github-actions github-actions bot removed the stable pr into a stable release branch label Dec 17, 2025
@ATGardner
Copy link
Contributor Author

/e2e

@ATGardner
Copy link
Contributor Author

/e2e

@ATGardner ATGardner merged commit 181c7ce into main Dec 17, 2025
5 checks passed
@ATGardner ATGardner deleted the CR-33086-fix-argo-server-crb branch December 17, 2025 10:57
ATGardner added a commit that referenced this pull request Dec 17, 2025
Ensure the RoleBinding kind is explicitly set to "RoleBinding"
and the role is set to "Role" for the app-proxy Argo workflows.
This change improves clarity and consistency in the RBAC configuration.
ATGardner added a commit that referenced this pull request Dec 17, 2025
based on #1008

Ensure the RoleBinding kind is explicitly set to "RoleBinding"
and the role is set to "Role" for the app-proxy Argo workflows.
This change improves clarity and consistency in the RBAC configuration.
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.

4 participants