-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Device plugin should only handle allocations of resources managed by it #53548
Labels
kind/bug
Categorizes issue or PR as related to a bug.
milestone/removed
sig/node
Categorizes an issue or PR as relevant to SIG Node.
Comments
k8s-github-robot
added
the
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
label
Oct 6, 2017
/sig node |
k8s-ci-robot
added
the
sig/node
Categorizes an issue or PR as relevant to SIG Node.
label
Oct 6, 2017
k8s-github-robot
removed
the
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
label
Oct 6, 2017
@vishh could you add this bug to the 1.8 milestone? Thanks a lot! |
jiayingz
added a commit
to jiayingz/kubernetes
that referenced
this issue
Oct 9, 2017
…#53548 that container allocation request may fail if it requests some extended resource not managed by any device plugin.
k8s-github-robot
pushed a commit
that referenced
this issue
Oct 9, 2017
Automatic merge from submit-queue (batch tested with PRs 52662, 53547, 53588, 53573, 53599). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. In DevicePluginHandlerImpl.Allocate(), skips untracked extended resou… …rces. Otherwise, we would fail a Pod allocation request that has an extended resource not managed by any device plugin. **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # #53548 **Special notes for your reviewer**: **Release note**: ```release-note Ignore extended resources that are not registered with kubelet ```
jiayingz
added a commit
to jiayingz/kubernetes
that referenced
this issue
Oct 9, 2017
…#53548 that container allocation request may fail if it requests some extended resource not managed by any device plugin.
[MILESTONENOTIFIER] Milestone Removed Important: This issue was missing labels required for the v1.9 milestone for more than 3 days: priority: Must specify exactly one of |
Fixed with PR #53547 |
jiayingz
added a commit
to jiayingz/kubernetes
that referenced
this issue
Jan 3, 2018
…#53548 that container allocation request may fail if it requests some extended resource not managed by any device plugin.
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.
milestone/removed
sig/node
Categorizes an issue or PR as relevant to SIG Node.
The resources managed by device plugin are a subset of the extended resources. The device plugin should only handle the resources managed by it, instead of all extended resources
kubernetes/pkg/kubelet/cm/device_plugin_handler.go
Line 169 in 2d16260
kubernetes/pkg/kubelet/deviceplugin/utils.go
Lines 57 to 61 in 2d16260
/kind bug
/assign @jiayingz
/cc @vishh
The text was updated successfully, but these errors were encountered: