Restrict K8s role definitions to actually needed roles

druid-io / druid-operator

Druid Kubernetes Operator

Other

205 stars 93 forks source link

Restrict K8s role definitions to actually needed roles #225

Closed DipeshCS closed 3 years ago

DipeshCS commented 3 years ago

We are planning to use Druid operator in Production at Zalando and we realized that k8s role definition is too generous giving access to lot more resources for operator than needed.

Few examples would be:

Usage of daemonsets is missing
Usage of servicemonitors is missing
Few resources use * but it is good practice to explicitly list them out and many more.

It would be great if it can be fixed and made production-ready. Let me know if you need more information.

Thanks

AdheipSingh commented 3 years ago

@DipeshCS agree with your observations and points listed out. Do you mind sending a patch and we can have it reviewed :) Thanks