-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Integrate docker with kubelet via CRI #31459
Comments
Automatic merge from submit-queue dockershim: use the new Metadata types and add more unit tests Part of #31459
Automatic merge from submit-queue dockershim: add unit tests for sandbox/container status Part of #31459
Got the first e2e result: |
Hmm, initcontainers are already addressed in #33363, port-forwarding is not implemented yet, we could deal it same with exec for docker. |
Claims port-forward for docker. Update: refer #33810. |
Claims attach for docker. Attach is also not implemented in kuberuntime yet. I'll verify with my local cluster even though the change is very small. :) Will send a PR soon after I verify it. PR #33815. |
Automatic merge from submit-queue Fake docker portfoward for in-process docker CRI integration This is necessary to pass e2e tests for in-process docker CRI integration. This is part of #31459. cc/ @Random-Liu @kubernetes/sig-node
Automatic merge from submit-queue Apply default image tags for all runtimes Move the docker-specific logic up to the ImageManager to allow code sharing among different implementations. Part of #31459 /cc @kubernetes/sig-node
Automatic merge from submit-queue CRI: Add presubmit CRI validation test. For #31459. This PR adds a new suite for CRI presubmit validation which runs non-flaky, non-serial, non-slow test per-pr. Except this PR, I'll also change the test-infra side. Ideally, after this is done, we should be be able to trigger CRI validation test per-pr with something like `@k8s-bot cri node e2e test this` and `@k8s-bot cri e2e test this`. @yujuhong @feiskyer @yifan-gu @freehan /cc @kubernetes/sig-node
…chmark Automatic merge from submit-queue CRI: Add serial and benchmark test suite. For #31459. The serial test result will be shown on test-grid. The benchmark test result will be shown [node-perf-dash](http://node-perf-dash.k8s.io/#/builds) This PR also changes the cri validation test to use the same gci image with node e2e instead of the canary image. The docker version is still 1.11.2. @yujuhong @feiskyer @yifan-gu /cc @kubernetes/sig-node
…rf-dash Automatic merge from submit-queue CRI: Add cri benchmark test in node perf dash. For kubernetes/kubernetes#31459. This depends on kubernetes/test-infra#761 and kubernetes/kubernetes#34141. After this gets merged, I'll restart node perf dash. Then we should be able to monitor benchmark result with cri enabled. @yujuhong @feiskyer /cc @kubernetes/sig-node
I run density test to compare operation latency with grpc/non-grpc integration. It turns out that the latency increment is acceptable, for example list_container latency is increased by 30%. However, the memory usage is increased a lot by about 80%: I'll run some test to analyze the memory usage increment. |
@yujuhong @Random-Liu This needs to be triaged as a release-blocker or not for 1.5 |
We completed all the p0/p1 items. Moving the issue to 1.6 to finish the rest. |
is it still planned for 1.6? |
Yes, we just enabled the CRI implementation by default in kubelet last night. |
great! does it mean that |
Closing this issue since the only thing left is the CRI validation test, which is tracked separately. |
Meta issue: #28789
This issue tracks the progress of docker integration via CRI.
The initial CRI server-side implementation for docker is in the
pkg/kubelet/dockershim
package. We chose to let the code remain in the kubelet codebase to help with the migration. It will also not go through grpc/protobuf until the features are completed.For 1.5, we aim to have a functional docker integration.
Implementation TODOs: #29478
Current integration CI Node E2E builder (#33189): https://k8s-testgrid.appspot.com/google-node#kubelet-cri-gce-e2e
Current integration CI E2E builder (kubernetes/test-infra#712): https://k8s-testgrid.appspot.com/google-gce#gci-gce-cri
Current presubmit builder:
@k8s-bot cri node e2e test this
to trigger node e2e test.@k8s-bot cri e2e test this
to trigger e2e test.@k8s-bot cri test this
to trigger both.Relevant PRs so far: #29700, #29553, #29580
Relevant issues: #29252
The text was updated successfully, but these errors were encountered: