We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.io
p2:manager running error,role.yaml missing some permissions defined
p3:use lastest code create crd to cluster,api-resources and role.yaml do not match
The text was updated successfully, but these errors were encountered:
@waney316 thanks for your work.
I don't find that the operator needs the configmap permission, could you confirm it again?
configmap
Sorry, something went wrong.
@waney316 thanks for your work. I don't find that the operator needs the configmap permission, could you confirm it again? @gobbq
I don't find that the operator needs the configmap permission, could you confirm it again? @gobbq
@waney316 Oh, I see. Thanks.
Merge pull request #108 from gobbq/fix-role-permissions
eefaec0
[ISSUE #107] Fix role permissions
No branches or pull requests
p1:role.yaml and role_binding.yaml name properties do not match,ClusterRoleBinding namespace should not specify default
p2:manager running error,role.yaml missing some permissions defined
p3:use lastest code create crd to cluster,api-resources and role.yaml do not match
The text was updated successfully, but these errors were encountered: