From f8682ac1bb9302775f24a1bb1929e02b0ee33cd7 Mon Sep 17 00:00:00 2001 From: Yifan Gu Date: Mon, 10 Oct 2016 19:07:54 -0700 Subject: [PATCH] More clarification on the in-process integration. --- docs/proposals/kubelet-rkt-runtime.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/proposals/kubelet-rkt-runtime.md b/docs/proposals/kubelet-rkt-runtime.md index e5a7bdc98c8..850b5a18e5c 100644 --- a/docs/proposals/kubelet-rkt-runtime.md +++ b/docs/proposals/kubelet-rkt-runtime.md @@ -77,6 +77,12 @@ This is, in no small part, to make it *Easy to Deploy*. Remaining in-process also helps this integration not regress on performance, one axis of being *Full-Featured*. +### Communicate through gRPC + +Although the kubelet and rktlet will be compiled together, the runtime and kubelet will still communicate through gRPC interface for better API abstraction. + +For the near short term, they will still talk through a unix socket before we implement a custom gRPC connection that skips the network stack. + ### Developed as a Separate Repository Brian Grant's discussion on splitting the Kubernetes project into [separate repos](https://github.com/kubernetes/kubernetes/issues/24343) is a compelling argument for why it makes sense to split this work into a separate repo. @@ -117,7 +123,8 @@ In the future, some of these decisions are expected to be changed such that rkt 3. rktlet integrate with kubelet, pass 100% e2e and node e2e tests, with nspawn stage1. 4. rktlet integrate with kubelet, pass 100% e2e and node e2e tests, with kvm stage1. -5. Revendor rktlet into `pkg/kubelet/rkt` to replace the current rkt. +5. Revendor rktlet into `pkg/kubelet/rktshim`, and start deprecating the `pkg/kubelet/rkt` package. +6. Eventually replace the current `pkg/kubelet/rkt` package.