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

node-feature-discovery-topology-updater failed to get kubelet config from configz endpoint: Forbidden #1098

Closed
andrewm41 opened this issue Mar 27, 2023 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@andrewm41
Copy link

andrewm41 commented Mar 27, 2023

What happened:

I've installed v0.12.1 with helm like this:

helm -n node-feature-discovery upgrade --install --wait node-feature-discovery . --set topologyUpdater.enable=true --set topologyUpdater.createCRDs=true --set topologyUpdater.rbac.create=true --set topologyUpdater.serviceAccount.create=true

but got this error in all node-feature-discovery-topology-updater pods:

F0327 15:25:37.787116 1 main.go:86] failed to get kubelet config from configz endpoint: Forbidden (user=system:serviceaccount:node-feature-discovery:node-feature-discovery-topology-updater, verb=get, resource=nodes, subresource=proxy)

What you expected to happen:
node-feature-discovery-topology-updater pods are up and running

Environment:

  • Kubernetes version (use kubectl version): 1.24
  • Cloud provider or hardware configuration: baremetal
  • OS (e.g: cat /etc/os-release): ubuntu 20.04
@andrewm41 andrewm41 added the kind/bug Categorizes issue or PR as related to a bug. label Mar 27, 2023
@marquiz
Copy link
Contributor

marquiz commented Mar 31, 2023

That's the problem that got fixed in master by #1078, I think. We could cut a quick patch release 🤔

@marquiz
Copy link
Contributor

marquiz commented Apr 1, 2023

@andrewm41 see #1109

@marquiz
Copy link
Contributor

marquiz commented Apr 3, 2023

Fixed in v0.12.2. @andrewm41 please report back if you have any further issues

/close

@k8s-ci-robot
Copy link
Contributor

@marquiz: Closing this issue.

In response to this:

Fixed in v0.12.2. @andrewm41 please report back if you have any further issues

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

No branches or pull requests

3 participants