Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes around the default argocd policy #6

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

mbaldessari
Copy link
Contributor

We do two main changes:

  1. We set the defaultPolicy to role:readonly. This allows any
    authenticated user to see the the argo applications
  2. We add a g, admin, role:admin and make sure that we get the email
    scope from the OIDC as well. This allows the RHDP user admin to
    work out of the box.

Tested as follows:

  1. Logged in on the clusterwide argo as kube admin and could still see all apps
    and could refresh/sync
  2. Logged in as htpasswd user foo and could see the apps in read-only and could
    not sync
  3. Logged in as htpasswd user admin and could see the apps and could
    sync/refresh them

Co-Authored-By: Akos Eros [email protected]

We do two main changes:
1. We set the `defaultPolicy` to `role:readonly`. This allows any
   authenticated user to see the the argo applications
2. We add a `g, admin, role:admin` and make sure that we get the `email`
   scope from the OIDC as well. This allows the RHDP user `admin` to
   work out of the box.

Tested as follows:
1. Logged in on the clusterwide argo as kube admin and could still see all apps
   and could refresh/sync
2. Logged in as htpasswd user foo and could see the apps in read-only and could
   not sync
3. Logged in as htpasswd user admin and could see the apps and could
   sync/refresh them

Co-Authored-By: Akos Eros <[email protected]>
@mbaldessari mbaldessari merged commit 18d286a into validatedpatterns:main Oct 16, 2024
3 checks passed
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.

1 participant