Closed schwesig closed 4 months ago
/CC @larsks @tssala23 @dystewart
Kruize Admins group has the same access to the cluster as we (nerc folks) do, we didn't create a new role just a new role binding (Kruize admins and nerc ops are both bound to the same role). There are some commands that they will not be able to do by default, but it they add the --as system:admin, flag to the command they'll be able to run it.
The cluster isn't currently setup with argoCD, so even though I've been making pull requests to change the manifests in the config repo, I've actually been applying them myself. Even once/if it has argoCD managing it my understanding is they can still install operators manually, they just can't make changes to anything that is managed by argoCD i.e. they couldn't remove an operator if argoCD is managing it unless the change the manifests on github.
As requested and approved with me, operator-install rights are applied for the web console. thanks @tssala23
closing this issue, and creating a new one for the details about using/not using ArgoCD/GitOps
Ensure the kruize-admins user group has the permissions to install operators.
Questions:
Related Issues and Pull Request:
Assigned: @tssala23 ? or change it, if I am wrong