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

charts: missing perms in ClusterRole if metricsCollector.enabled is true #1597

Open
linuxmaniac opened this issue Jan 3, 2025 · 1 comment · May be fixed by #1599
Open

charts: missing perms in ClusterRole if metricsCollector.enabled is true #1597

linuxmaniac opened this issue Jan 3, 2025 · 1 comment · May be fixed by #1599
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@linuxmaniac
Copy link
Contributor

What version of descheduler are you using?

descheduler version: v0.32.0

Does this issue reproduce with the latest release?

It's the latest one

Which descheduler CLI options are you using?

Please provide a copy of your descheduler policy config file

deschedulerPolicy:
      nodeSelector: node-role.kubernetes.io/worker=true
      metricsCollector:
        enabled: true

What k8s version are you using (kubectl version)?

kubectl version Output
$ kubectl version
Client Version: v1.31.4
Kustomize Version: v5.4.2
Server Version: v1.31.2

What did you do?

enabled metricsCollector

What did you expect to see?

What did you see instead?

E0103 12:37:27.584970       1 metricscollector.go:128] "Error fetching metrics" err="nodes.metrics.k8s.io \"k3s-node3\" is forbidden: User \"system:serviceaccount:kube-system:descheduler\" cannot get resource \"nodes\" in API group \"metrics.k8s.io\" at the cluster scope" node="k3s-node3"
@linuxmaniac linuxmaniac added the kind/bug Categorizes issue or PR as related to a bug. label Jan 3, 2025
@cayla
Copy link
Contributor

cayla commented Jan 7, 2025

Dupe of #1595

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants