// +kubebuilder:rbac Generates ClusterRole with name "manager-role", How to change this name ?.

[SAbdulRahuman]

Hi ,
I'm using +kubebuilder markers to generate RBAC ClusterRoles, for example below are the markers i have created

// +kubebuilder:rbac:groups=apps,resources=deployments,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=apps,resources=replicasets,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=core,resources=pods,verbs=get;list;watch;create;
// +kubebuilder:rbac:groups=core,resources=services,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=core,resources=configmaps,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=core,resources=serviceaccounts,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=core,resources=configmaps,verbs=get;list;watch;create;update;patch;delete
// +kubebuilder:rbac:groups=core,resources=replicasets,verbs=get;list;watch;create;update;patch;delete

Kubebuilder generated ClusterRole role.yaml with name as manager-role but i want to different name. How to mentioned kubebuilder to generate the ClusterRole with differrrent name ?

For example, Below the ClusterRole got generated

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  creationTimestamp: null
  name: manager-role
rules:
- apiGroups:
  - apps
  resources:
  - deployments
  verbs:
  - create
  - delete
  - get
  - list
  - patch
  - update
  - watch

My question is, How to change name: manager-role to name: test-role

[NarayanSampathKumar]

Hi Please let me know if you have found anything on this, im also facing this issue.
How to change the name should we create a new controller for that or is there any other way. I am fairly new to this but working on operator as a fresher. Please guide me on this as it would be very much helpful for me because i am stuck with this for a couple of days. Please help me out on this.

[serhermar]

Hi!

role.yaml file is generated through the marker:

// +kubebuilder:rbac:groups=apps,resources=deployments,verbs=get;list;watch;create;update;patch;delete

If you add namespace=xxxxx to the marker:

// +kubebuilder:rbac:groups=apps,namespace=xxxxxx,resources=deployments,verbs=get;list;watch;create;update;patch;delete

The role.yaml file is generated in Role format.

You can check the documentation in here

[filintod]

I was looking into this, and this is not controlled by the markers but by the Makefile template

kubebuilder/pkg/plugins/golang/v2/scaffolds/internal/templates/makefile.go

Line 94 in 6109ce1

$(CONTROLLER_GEN) $(CRD_OPTIONS) rbac:roleName=manager-role webhook paths="./..." output:crd:artifacts:config=config/crd/bases

.

[camilamacedo86]

The permissions are generate according to the markers defined in the controller
Example: https://github.com/kubernetes-sigs/kubebuilder/blob/master/testdata/project-v4-with-deploy-image/internal/controller/busybox_controller.go#L63-L69

Those will be generate via controller-gen when you run make manifests and make generate

Please note that go/v2, and go/v3 layouts are deprecated and no longer used.
So, if you run kubebuilder init you will have the default scaffold of go/v4 (https://github.com/kubernetes-sigs/kubebuilder/tree/master/pkg/plugins/golang/v4)
Example of the result can be found in: https://github.com/kubernetes-sigs/kubebuilder/tree/master/testdata/project-v4

So, you can look the Makefile of the example

ALso, I would recommend you upgrade your project to use the latest layout available.

Closing this one as answered as well
However, if you need feel free to re-open.