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
Describe the bug
The logic introduced to the helm chart in #16091 causes an error when using non-namespaced RBAC. This logic appears to intend to switch between RoleBinding and ClusterRoleBinding, but instead switches between RoleBinding and ClusterBinding which is not valid. This leads to an error on chart deployment - ClusterBinding.rbac.authorization.k8s.io "" not found. The logic should be:
{{ if not .Values.rbac.namespaced }}ClusterRole{{ else }}Role{{ end }}Binding
To Reproduce
Steps to reproduce the behavior:
Deploy Loki with Helm chart version >= 6.13.0
Expected behavior
If namespaced RBAC is not enabled, the deployment should properly create a ClusterRoleBinding.
Environment:
Infrastructure: Kubernetes
Deployment tool: helm
The text was updated successfully, but these errors were encountered:
Describe the bug
The logic introduced to the helm chart in #16091 causes an error when using non-namespaced RBAC. This logic appears to intend to switch between
RoleBinding
andClusterRoleBinding
, but instead switches betweenRoleBinding
andClusterBinding
which is not valid. This leads to an error on chart deployment -ClusterBinding.rbac.authorization.k8s.io "" not found
. The logic should be:To Reproduce
Steps to reproduce the behavior:
Expected behavior
If namespaced RBAC is not enabled, the deployment should properly create a
ClusterRoleBinding
.Environment:
The text was updated successfully, but these errors were encountered: