You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
Fresh helm install of dcontroller fails — the controller cannot start:
operators.dcontroller.io is forbidden: User "system:serviceaccount:dcontroller-system:dcontroller-account"
cannot list resource "operators" in API group "dcontroller.io" at the cluster scope:
RBAC: clusterrole.rbac.authorization.k8s.io "dcontroller-role" not found
Root Cause
config/rbac/role.yaml uses name: manager-role. With namePrefix: dcontroller in config/helm-base/kustomization.yaml, kustomize produces dcontrollermanager-role (no dash).
The ClusterRoleBinding in config/rbac/role_binding.yaml hardcodes roleRef.name: dcontroller-role, which doesn't match.
All other RBAC resources use the -prefix convention (-rolebinding, -account, -leader-election-role) which produces correct names with the namePrefix.
Timeline
Oct 29 (6803f35): namePrefix: dcontroller introduced in kustomize pipeline
Dec 9-19: Published chart packages still used previous all.yaml — worked fine
Jan 10 (c8d3481 on gh-pages): Automated rebuild regenerated chart via kustomize — broke RBAC