-
Notifications
You must be signed in to change notification settings - Fork 42k
Move external facing kubelet apis to staging #83551
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
Move external facing kubelet apis to staging #83551
Conversation
Change-Id: I06adcb43bd278b430ffad2010869e1524c8cc4ff
Change-Id: Ia3917cec1453c0b22a958faf8c22bccd79242d14
|
/sig node |
Change-Id: Ib5a0d3b3e9bd1505a263064f35bea3514c992e4a
|
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. |
|
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. |
Change-Id: I6535b506f50558b31663a13cd270b15023afa2c6
|
@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 |
|
of course the ultimate arbiter is sig-node here :) cc @derekwaynecarr @dchen1107 |
|
/test pull-kubernetes-kubemark-e2e-gce-big |
|
@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 |
if that's the case, that would seem to make sense. will defer to sig-node reviewers |
|
/assign @dashpole kubelet repo sounds fine IMO |
|
kubelet repo sgtm |
|
/assign @derekwaynecarr @liggitt |
|
I am fine with the kubelet repo. Moving this out of k/k into a more focused repo is the right thing. /approve |
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
…belet-apis-to-staging Move external facing kubelet apis to staging
|
Should we move the Or are we waiting for it to graduate to beta? |
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]>
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]>
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]>
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]>
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]>
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]>
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]>
* 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]>
What type of PR is this?
/kind api-change
/area code-organization
What this PR does / why we need it:
devicepluginandpluginregistrationare external facing APIs. currently we are forcing folks to import them fromk8s.io/kuberneteswhich is not optimal. We should instead make them available from thek8s.io/kubeletrepo 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?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: