Repository navigation
deploy yaml error #107
Description
p1：role.yaml and role_binding.yaml name properties do not match，ClusterRoleBinding namespace should not specify default
---
# role.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
creationTimestamp: null
name: manager-role # not match# role_binding.yaml
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: rocketmq-operator
subjects:
- kind: ServiceAccount
name: rocketmq-operator
namespace: default
roleRef:
kind: ClusterRole
name: rocketmq-operator # not match
apiGroup: rbac.authorization.k8s.iop2：manager running error，role.yaml missing some permissions defined
- get configmap is forbiden
- get resources not found
p3：use lastest code create crd to cluster，api-resources and role.yaml do not match
Activity
gobbq commentedon Jul 4, 2022
@waney316 thanks for your work.
I don't find that the operator needs the
configmappermission, could you confirm it again?waney316 commentedon Jul 4, 2022
gobbq commentedon Jul 4, 2022
@waney316 Oh, I see. Thanks.
Merge pull request #108 from gobbq/fix-role-permissions
RockteMQ-AI commentedon Aug 11, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedThis is a valid bug — the
role.yamlandrole_binding.yamlhave mismatched names:role.yamldefinesClusterRolenamedmanager-rolerole_binding.yamlreferencesClusterRolenamedrocketmq-operatorAdditionally, the
ClusterRoleis missing permissions forconfigmapsand other resources the operator needs.Fix: Align the names and add the missing permissions to the
ClusterRole.Automated evaluation by github-manager