node-feature-discovery
node-feature-discovery copied to clipboard
kubernetes-sigs
Does NDF publishes the node features to the kubelet?
So pods can request a pci device or other hardware (similar to device plugin api)
So pods can request a pci device or other hardware (similar to device plugin api)
NFD does not register any device plugin resources. It can label nodes based on which PCI devices are available. These labels can then be used by device plugins daemonsets to get their pods only to those nodes that have the right devices.
Are there any plans in the future for NDF to publish resources to the kubelet?
Device plugin resources? I don't think so (vendors have their device plugins implemented for this). Is there a particular device or resource you would want to use?
We added experimental "Extended Resources" support to NFD some time ago: https://kubernetes-sigs.github.io/node-feature-discovery/v0.7/get-started/features.html#extended-resources
Just to be clear, it is by no means a replacement for the usage of device plugins. The device plugin API does more than just expose a feature/resource as an extended resource. NFD will not do any allocate/deallocate calls or health checks.
It seems to me that NDF and device plugin capabilities go hand in hand, why not combine them?
Device plugins are much more than just updating the node status (advertising the extended resource(s)). We don't want to have vendor-specific device management logic in NFD and I don't think the vendors want it either 🙂
As Zvonko mentioned, NFD has this experimental feature of advertising extended resources but there is no way to add any device plugin functionality.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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.
