Lack of account management system

[zhaomingcheng01]

Different namespaces are projects that are responsible for by different project teams, and after unified installation by the administrator, the operator should distinguish according to the namespace, similar to argocd has an account authorization system,It is better to be integrated into argocd, and can observe the health status of the pod, and can directly operate argo-rollouts, avoiding the need to operate argo-rollouts first, and then on argocd to observe whether the service status is started normally

[kostis-codefresh]

If you are asking about general RBAC, this should be possible with the built-in Kubernetes RBAC https://kubernetes.io/docs/reference/access-authn-authz/rbac/

If you are talking about the UI then is this a duplicate of #1323 ?

[zhaomingcheng01]

Can the ui interface provide the same account authorization system as argocd, otherwise it can only be operated by the administrator,Is a problem