forked from roger/k3s-cluster
e4b597be15
The platform-engineer ArgoCD account was created in argocd-cm.yaml but had no RBAC role binding, causing 403 permission denied on all API calls to /api/v1/applications/<name>. This adds argocd-rbac-cm.yaml granting the platform-engineer role full access to applications, projects, clusters, and repositories.
17 lines
500 B
YAML
17 lines
500 B
YAML
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: argocd-rbac-cm
|
|
namespace: argocd
|
|
labels:
|
|
app.kubernetes.io/name: argocd-rbac-cm
|
|
app.kubernetes.io/part-of: argocd
|
|
data:
|
|
policy.default: role:readonly
|
|
policy.csv: |
|
|
p, role:platform-engineer, applications, *, */*, allow
|
|
p, role:platform-engineer, projects, *, *, allow
|
|
p, role:platform-engineer, clusters, *, *, allow
|
|
p, role:platform-engineer, repositories, *, *, allow
|
|
g, platform-engineer, role:platform-engineer
|