Skip to content

Conversation

@dims
Copy link
Member

@dims dims commented Oct 6, 2019

What type of PR is this?
/kind api-change
/area code-organization

What this PR does / why we need it:
deviceplugin and pluginregistration are external facing APIs. currently we are forcing folks to import them from k8s.io/kubernetes which is not optimal. We should instead make them available from the k8s.io/kubelet repo to make it easier for them.

Which issue(s) this PR fixes:

Related to #82437

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

external facing APIs in pluginregistration and deviceplugin packages are now available under k8s.io/kubelet/pkg/apis/

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


dims added 2 commits October 6, 2019 15:28
Change-Id: I06adcb43bd278b430ffad2010869e1524c8cc4ff
Change-Id: Ia3917cec1453c0b22a958faf8c22bccd79242d14
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/code-organization Issues or PRs related to kubernetes code organization cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/kubelet area/test sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 6, 2019
@dims
Copy link
Member Author

dims commented Oct 6, 2019

/sig node
/priority important-soon

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Oct 6, 2019
@k8s-ci-robot k8s-ci-robot requested review from ixdy and klueska October 6, 2019 19:46
Change-Id: Ib5a0d3b3e9bd1505a263064f35bea3514c992e4a
@k8s-ci-robot k8s-ci-robot added the area/dependency Issues or PRs related to dependency changes label Oct 6, 2019
@klueska
Copy link
Contributor

klueska commented Oct 6, 2019

What implications does this have if we have changes to these APIs in future releases? I know of at least one addition to the device plugin API coming in 1.17.

@fejta-bot
Copy link

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

@neolit123
Copy link
Member

LGTM
/assign @sttts @mtaufen

Change-Id: I6535b506f50558b31663a13cd270b15023afa2c6
@dims
Copy link
Member Author

dims commented Oct 6, 2019

@klueska we talked about this in the code-organization sub project (sig-arch) and the consensus at least there was that it's worse to force people to import kubernetes/kubernetes than to change things. even when it is in kubernetes/kubernetes, we end up changing stuff anyway and we force people to deal with the breakages. So how will the situation be any different was the thought. One thing better than current situation is that at least they will NOT be forced to import k/k and can use k8s.io/kubelet.

cc @liggitt @smarterclayton

@dims
Copy link
Member Author

dims commented Oct 6, 2019

of course the ultimate arbiter is sig-node here :) cc @derekwaynecarr @dchen1107

@dims
Copy link
Member Author

dims commented Oct 6, 2019

/test pull-kubernetes-kubemark-e2e-gce-big

@dims
Copy link
Member Author

dims commented Oct 7, 2019

@liggitt i debated that as well. both the packages are unusable outside of their current use case of integration with kubelet, and there are 2 of them, so i picked k8s.io/kubelet

@liggitt
Copy link
Member

liggitt commented Oct 7, 2019

both the packages are unusable outside of their current use case of integration with kubelet, and there are 2 of them, so i picked k8s.io/kubelet

if that's the case, that would seem to make sense. will defer to sig-node reviewers

@mtaufen
Copy link
Contributor

mtaufen commented Oct 8, 2019

/assign @dashpole
for an official opinion.

kubelet repo sounds fine IMO

@dashpole
Copy link
Contributor

dashpole commented Oct 8, 2019

kubelet repo sgtm

@dims
Copy link
Member Author

dims commented Oct 9, 2019

/assign @derekwaynecarr @liggitt

@derekwaynecarr
Copy link
Member

I am fine with the kubelet repo.

Moving this out of k/k into a more focused repo is the right thing.

/approve
/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 10, 2019
@dchen1107
Copy link
Member

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dchen1107, derekwaynecarr, dims

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 10, 2019
@mtaufen
Copy link
Contributor

mtaufen commented Oct 10, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot merged commit 3db6d3a into kubernetes:master Oct 10, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Oct 10, 2019
ohsewon pushed a commit to ohsewon/kubernetes that referenced this pull request Oct 16, 2019
…belet-apis-to-staging

Move external facing kubelet apis to staging
@RenaudWasTaken
Copy link
Contributor

RenaudWasTaken commented Oct 23, 2019

Should we move the podresources directory as well? It's pretty tied to device support as it allows to tie device metrics to pods and containers.

Or are we waiting for it to graduate to beta?
cc @dims

nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Dec 17, 2019
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Dec 19, 2019
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Jan 16, 2020
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Jan 17, 2020
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Jan 20, 2020
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Jan 23, 2020
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev pushed a commit to nickolaev/networkservicemesh that referenced this pull request Jan 23, 2020
As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>
haiodo pushed a commit to networkservicemesh/networkservicemesh that referenced this pull request Jan 27, 2020
* Remove the controllers/sriov-controller

That is a very outdated code and concept nto relevant anymore.
Get rid of it and the whole folder tree to support it.

Signed-off-by: Nikolay Nikolaev <[email protected]>

* Switch to K8s v1.17.0

Signed-off-by: Nikolay Nikolaev <[email protected]>

* In k8s v1.17.0 the kubelet API has moved

As per kubernetes/kubernetes#83551

External facing APIs in plugin registration and device plugin
packages are now available under k8s.io/kubelet/pkg/apis/

Signed-off-by: Nikolay Nikolaev <[email protected]>

* Change the k8s version to v1.17.0 when we int the cluster

Packet and Vagrant deplyments wil default to v1.17.0 now.

Signed-off-by: Nikolay Nikolaev <[email protected]>

* Adapt the tests/fake_client.go to latest API

This file is almost an exact copy of
https://github.com/kubernetes/client-go/blob/master/rest/fake/fake.go

So just import it and adjust names where needed.

Signed-off-by: Nikolay Nikolaev <[email protected]>

* go mod tidy after a rebase

Signed-off-by: Nikolay Nikolaev <[email protected]>

* K8s v1.17.1

Signed-off-by: Nikolay Nikolaev <[email protected]>

* Cleanups after rebase to master

Signed-off-by: Nikolay Nikolaev <[email protected]>

* Remove refereces to v0.2.0

Signed-off-by: Nikolay Nikolaev <[email protected]>
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. area/code-organization Issues or PRs related to kubernetes code organization area/dependency Issues or PRs related to dependency changes area/kubelet area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.