-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClusterRole creation doesn't happen #1407
Comments
I think this relates to this PR (and change) and my comment #1379 (comment). ClusterRole and ClusterRoleBinding where ressources of the helm deployment before that change. And with that change they become hook resources. You need to install the ClusterRole and ClusterRoleBinding by yourself, after you perfom the helm upgrade of the operator to version 1.1.10. After that they stay or are recreated when performing helm upgrade due to the hook-policies. |
And I think besides |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Even when setting rbac.createClusterRole to true, I have never seen the chart create the actual cluster role.
I don't see what the issue is myself in the helm code. That value is default true anyway, but when creating the helm chart, no ClusterRole appears for me, and the pod logs rbac erros. Maybe something to do with the helm hooks? The installation succeeded as far as helm is concerned.
I started with Chart version 1.1.0 and updated to 1.1.13, but ultimately I had to create the cluster role & binding outside of helm to workaround the rbac issues.
The text was updated successfully, but these errors were encountered: