-
Notifications
You must be signed in to change notification settings - Fork 247
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
Improved readiness probe for nfd-worker #1806
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
marquiz
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jul 23, 2024
ping @omerap12 😊 |
yeap :) |
Draft
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Oct 21, 2024
/remove-lifecycle stale |
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
What would you like to be added:
Improve the gRPC health server so that it doesn't report ready/live until the feature discovery has succeeded and the NodeFeature CR object has been created/updated.
Why is this needed:
Better reflect the actual readiness nfd-worker.
The text was updated successfully, but these errors were encountered: