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

Failed to watch NodeFeatureGroup #248

Open
mausch opened this issue Jul 22, 2024 · 2 comments
Open

Failed to watch NodeFeatureGroup #248

mausch opened this issue Jul 22, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@mausch
Copy link

mausch commented Jul 22, 2024

What happened:

Installed operator as documented in https://kubernetes-sigs.github.io/node-feature-discovery/master/deployment/operator.html#deployment

master nodes keep failing with the following error:

failed to list *v1alpha1.NodeFeatureGroup: the server could not find the requested resource (get nodefeaturegroups.nfd.k8s-sigs.io)
Failed to watch *v1alpha1.NodeFeatureGroup: failed to list *v1alpha1.NodeFeatureGroup: the server could not find the requested resource (get nodefeaturegroups.nfd.k8s-sigs.io)

Indeed no NodeFeatureGroup CRD was created.

What you expected to happen:

No failures.

How to reproduce it (as minimally and precisely as possible):

Install https://kubernetes-sigs.github.io/node-feature-discovery/master/deployment/operator.html#deployment on EKS.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): v1.28.9-eks-036c24b
  • Cloud provider or hardware configuration: EKS
  • OS (e.g: cat /etc/os-release): Amazon Linux 2
  • Kernel (e.g. uname -a):
  • Install tools:
  • Network plugin and version (if this is a network-related bug):
  • Others:
@mausch mausch added the kind/bug Categorizes issue or PR as related to a bug. label Jul 22, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 20, 2024
@mausch
Copy link
Author

mausch commented Oct 21, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2024
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