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

In DevicePluginHandlerImpl.Allocate(), skips untracked extended resou… #53547

Merged
merged 1 commit into from
Oct 9, 2017

Conversation

jiayingz
Copy link
Contributor

@jiayingz jiayingz commented Oct 6, 2017

…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:

Ignore extended resources that are not registered with kubelet during container resource allocation.

@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 6, 2017
…rces.

Otherwise, we would fail a Pod allocation request that has an extended
resource not managed by any device plugin.
@jiayingz
Copy link
Contributor Author

jiayingz commented Oct 6, 2017

/assign @yguo0905

@yguo0905
Copy link
Contributor

yguo0905 commented Oct 6, 2017

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 6, 2017
@feiskyer
Copy link
Member

feiskyer commented Oct 9, 2017

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 9, 2017
@jiayingz
Copy link
Contributor Author

jiayingz commented Oct 9, 2017

/assign @dchen1107

@dchen1107
Copy link
Member

Can I suggest to add a regression test which expose the issue without this pr and fixed by with it?

@jiayingz
Copy link
Contributor Author

jiayingz commented Oct 9, 2017

Thanks a lot for the suggestion, @dchen1107 . I will try to add an e2e or e2e_node test to expose this issue. In terms of timing, we do hope this fix can be picked into 1.8.1. I will check with the release manager to see when 1.8.1 will be cut.

@vishh
Copy link
Contributor

vishh commented Oct 9, 2017

A unit test might suffice for this PR. Given the timeline I'm OK with approving this as long as you can add unit tests soon(ish).
/lgtm
/approve 53548

@vishh vishh added this to the v1.8 milestone Oct 9, 2017
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Oct 9, 2017
@jiayingz
Copy link
Contributor Author

jiayingz commented Oct 9, 2017

Thanks a lot for the review! Just for this bug, I think we may extend the existing TestPodContainerDeviceAllocation() to expose it. I am working on that right now. We do want to have an integration test to exercise the whole non device-plugin extended resource scheduling. I found there is actually a test/e2e/scheduling/opaque_resource.go e2e test but unfortunately it was disabled due to flakiness. I will see whether I can extend the existing gpu_device_plugin e2e_node test with some additional extended resources.

@vishh vishh added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 9, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiayingz, vishh, yguo0905

Associated issue: 53548

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@jiayingz
Copy link
Contributor Author

jiayingz commented Oct 9, 2017

FYI, the unit test PR #53607.

@k8s-github-robot
Copy link

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 here.

@k8s-github-robot k8s-github-robot merged commit c12dab3 into kubernetes:master Oct 9, 2017
@jpbetz jpbetz added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 9, 2017
k8s-github-robot pushed a commit that referenced this pull request Oct 10, 2017
…47-upstream-release-1.8

Automatic merge from submit-queue.

Automated cherry pick of #53547

Cherry pick of #53547 on release-1.8.

#53547: In DevicePluginHandlerImpl.Allocate(), skips untracked

```release-note
Ignore extended resources that are not registered with kubelet during container resource allocation.
```
@k8s-cherrypick-bot
Copy link

Commit found in the "release-1.8" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants