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 is being created despite rbac.create set to false #14369

Open
mac133k opened this issue Oct 3, 2024 · 0 comments
Open

ClusterRole is being created despite rbac.create set to false #14369

mac133k opened this issue Oct 3, 2024 · 0 comments

Comments

@mac133k
Copy link

mac133k commented Oct 3, 2024

Describe the bug
Helm deployments using chart v6.15.0 and 6.16.0 fail with the following error (redacted):

Error: UPGRADE FAILED: Unable to continue with update: could not get information about the resource ClusterRole "loki-clusterrole" in namespace "": clusterroles.rbac.authorization.k8s.io "loki-clusterrole" is forbidden: User "*****" cannot get resource "clusterroles" in API group "rbac.authorization.k8s.io" at the cluster scope

In my values.yaml I put these lines:

rbac:
  create: false

Helm deployments used to succeed without errors until chart v6.12.0 - if I specify this version I am able to deploy Loki.

To Reproduce
Steps to reproduce the behavior:

  1. helm upgrade loki grafana/loki -f values.yaml -n my-namespace --version 6.15.0 = FAIL
  2. helm upgrade loki grafana/loki -f values.yaml -n my-namespace --version 6.16.0 = FAIL
  3. helm upgrade loki grafana/loki -f values.yaml -n my-namespace --version 6.12.0 = SUCCESS

Expected behavior
I expected Helm deployment from the latest chart to succeed.

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: Helm
  • Deployment mode: distributed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant