-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
Separate out cri related code into self contained package #90552
Separate out cri related code into self contained package #90552
Conversation
2cd8478
to
01b7bb2
Compare
/release-note-none |
/assign @derekwaynecarr @yujuhong @Random-Liu |
/assign @tallclair |
I think we're on the same page conceptually @dims ! Thank you for your work here. I'll defer to one of the other folks tagged around the details, as they have a more complete picture of the whole system than I do. |
@derekwaynecarr @liggitt here's the plan on the containerd side containerd/cri#1479 (comment) |
@dimms I think you meant to link to containerd/cri#1463 1479 is a different issue.. (that of merging the containerd/containerd and containerd/cri repos.) |
whoops! thanks @mikebrow |
I tried to think if I had any alternate options for splitting this out, but nothing struck me, so this will do for now. /approve |
Signed-off-by: Davanum Srinivas <[email protected]>
Signed-off-by: Davanum Srinivas <[email protected]>
Signed-off-by: Davanum Srinivas <[email protected]>
Signed-off-by: Davanum Srinivas <[email protected]>
0dc69ee
to
c7e79d2
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, dims, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kubernetes-node-e2e |
/retest |
/test pull-kubernetes-node-e2e |
1 similar comment
/test pull-kubernetes-node-e2e |
This change should've highlighted that |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Previous attempts to extract cri related code met with stiff resistance. We had PRs earlier to move streaming to staging/ etc. So in this PR we just consider moving code into a package that be used standalone w/o dragging in all of k/k.
Essentially the
pkg/kubelet/cri
uses only stuff in staging/ and does not use anything else inside k8s.io/kubernetes. We have a new .import-restrictions in that directory to ensure that things stay that way.two things to note:
Also note that i've prototyped this on the containerd/cri side as well:
containerd/cri#1463
If we do this,
containerd/cri
repo vendor/ directory will pull in 15k LOC less than they do todayWhich issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: