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
When making use of the new crd helm chart and setting crdwebhook.enabled to false for the core helm chart as suggested this leads to ClusterRoles and ClusterRoleBindings related to the custom resource definitions not being created by the core helm chart.
The ClusterRoles and ClusterRolebindings defined in the crd-role.yaml and crd-role-least.yaml templates are still needed when making use of the new crd helm chart and should therefore not be disabled when crdwebhook.enabled is set to false.
I suggest adding a new value crd.rbac.enabled which is by default set to true to control creation of the crd related RBAC resources instead.
The text was updated successfully, but these errors were encountered:
Summary
When making use of the new
crd
helm chart and settingcrdwebhook.enabled
tofalse
for thecore
helm chart as suggested this leads to ClusterRoles and ClusterRoleBindings related to the custom resource definitions not being created by thecore
helm chart.Reproduction
helm template neuvector-core .\charts\core\ --set crdwebhook.enabled=false -s templates/crd-role.yaml
Suggestion
The ClusterRoles and ClusterRolebindings defined in the
crd-role.yaml
andcrd-role-least.yaml
templates are still needed when making use of the newcrd
helm chart and should therefore not be disabled whencrdwebhook.enabled
is set to false.I suggest adding a new value
crd.rbac.enabled
which is by default set totrue
to control creation of the crd related RBAC resources instead.The text was updated successfully, but these errors were encountered: