Propagate Role/RoleBinding and ClusterRole/ClusterRoleBinding from ConfigMap to CustomConfigMap

[gopaddle-io]

Is your feature request related to a problem? Please describe. No

Describe the solution you'd like Provide a capability to set Cluster wide (ClusterRole and ClusterRoleBinding) and namespace specific (Role and RoleBinding) to ConfigMaps and propagate those permissions to the newly create CustomConfigMaps and CustomSecrets. Follow the blog for more information on creating Roles and RoleBindings.

Steps to validate:

1. Create a namespace
2. Create a ConfigMap in that namespace
3. Create a Secret in that namespace
4. Create a Service Account
5. Create a ClusterRole with verbs 'get' and 'list' on resources 'configmap' and 'secret'
6. Create a ClusterRoleBinding to reference the ClusterRole created in step 4
7. Create a Role with verbs 'get' and 'list' on resources 'configmap' and 'secret'
8. Create a RoleBinding to reference the Role created in step 7 along with the namespace created in step 1
9. Install Configurator
10. Get the ClusterRole and Role created in steps 4 and 7. The CustomConfigMap and CustomSecret resources should have the permissions for 'get' and 'list'.

Describe alternatives you've considered None

Additional context None

[gopaddle-io]

Please send pull requests to SODACODE-2022