Skip to content
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

Closed
autarchprinceps opened this issue Nov 24, 2021 · 4 comments
Closed

ClusterRole creation doesn't happen #1407

autarchprinceps opened this issue Nov 24, 2021 · 4 comments

Comments

@autarchprinceps
Copy link

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.

@jehof
Copy link

jehof commented Dec 1, 2021

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.

@cwyl02
Copy link
Contributor

cwyl02 commented Apr 6, 2022

And I think besides pre-install, we would also need pre-upgrade in helm.sh/hook

Copy link

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.

Copy link

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants