forked from roger/k3s-cluster
fix(argocd): add RBAC ConfigMap granting platform-engineer account read+sync access
The platform-engineer ArgoCD account was created (argocd-cm.yaml) with apiKey capability, but no argocd-rbac-cm ConfigMap existed, so the account had default (empty) RBAC and every API call returned 403. This adds the RBAC policy granting the platform-engineer role: - get applications (all projects/namespaces) - sync applications (all projects/namespaces) - get projects Needed for the platform-engineer cron jobs to read app health and trigger syncs via the ArgoCD API.
This commit is contained in:
15
argocd/argocd-rbac-cm.yaml
Normal file
15
argocd/argocd-rbac-cm.yaml
Normal file
@@ -0,0 +1,15 @@
|
|||||||
|
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: ""
|
||||||
|
policy.csv: |
|
||||||
|
p, role:platform-engineer, applications, get, */*, allow
|
||||||
|
p, role:platform-engineer, applications, sync, */*, allow
|
||||||
|
p, role:platform-engineer, projects, get, *, allow
|
||||||
|
g, platform-engineer, role:platform-engineer
|
||||||
Reference in New Issue
Block a user