If enablePodSecurityPolicies is set to false, ClusterRole fails validation

[skj-dev]

The default value of enablePodSecurityPolicies is false. That value is placed above the rules: section in server-clusterrole.yaml, which causes a broken ClusterRole resource to be described because the rules: section is mandatory.

The chart kicks out with:

Error: validation failed: error validating "": error validating data: ValidationError(ClusterRole): missing required field "rules" in io.k8s.api.rbac.v1.ClusterRole

unless enablePodSecurityPolicies is set to true.

[EDGsheryl]

I have encountered the same situation. It seems like that helm-v2.14.0 caused this problem.

when I revert my helm to v2.13.0, the helm works.

I supposed that rules: should be set null but I failed. So I downgraded my helm =A=.....

[adilyse]

Hi, thanks for reporting this issue! Since this appears to be related to the Helm version issue also reported in #178, I'm going to close so there isn't a duplicate. Please feel free to track the status of the issue there.

[diegopaludo]

Hi,
I have encountered the same situation. :(
I solved it by upgrading to version v2.14.1 of helm

[dignajar]

Perfect, thanks!

For users with Mac OS and installed via Helm via Brew.

brew upgrade kubernetes-helm
helm init --service-account tiller --upgrade