You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a resource is cluster wide, e.g. Destinations, you must ensure that you use a ClusterRole instead of a Role to give permissions to it. In the rbac.permissions feature this is done by setting resourceNamespace: "*", which could easily be forgotten.
this will create a Role/RoleBinding, however the Role will be useless, since it refererences a cluster-wide resource that isn't namespaced. We should emit a warning/error on validating webhook when this happens, and suggest that they change it to:
If a resource is cluster wide, e.g.
Destinations
, you must ensure that you use aClusterRole
instead of aRole
to give permissions to it. In therbac.permissions
feature this is done by settingresourceNamespace: "*"
, which could easily be forgotten.Example:
this will create a
Role
/RoleBinding
, however theRole
will be useless, since it refererences a cluster-wide resource that isn't namespaced. We should emit a warning/error on validating webhook when this happens, and suggest that they change it to:The text was updated successfully, but these errors were encountered: