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

Deprecate dockershim in vendor and change to use new containerd based architecture #323

Closed
resouer opened this Issue Mar 30, 2018 · 10 comments

Comments

Projects
None yet
4 participants
@resouer
Copy link
Member

resouer commented Mar 30, 2018

As the title said.

The code change will happen in this branch: https://github.com/kubernetes/frakti/tree/containerd-kata

And eventually be spitted to merge part to containerd org and others frakti master branch.

@t3hmrman

This comment has been minimized.

Copy link

t3hmrman commented Apr 3, 2018

Just wanted to note that Frakti v2 looks really exciting to me -- one of my biggest wants was to use frakti as it exists now with cri-containerd (which is what I run now). It looks like frakti v2 will "upgrade" (IMO, some may not consider docker -> containerd an upgrade possibly) both the runV side and the docker side.

Actually came in to make a ticket requesting clarification on how to use containerd instead of docker but looks like I won't need to :)

@resouer

This comment has been minimized.

Copy link
Member

resouer commented Apr 3, 2018

@t3hmrman Exactly, we are actively working on containerd + Kata with folks from Google and Hyper. There will be no docker & dockershim needed in the frakti v2 project.

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jul 2, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Aug 1, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@resouer

This comment has been minimized.

Copy link
Member

resouer commented Aug 30, 2018

The containerd plugin has been temporarily implemented on this dev branch: https://github.com/hyperhq/kata-runtime/tree/shimv2

@t3hmrman

This comment has been minimized.

Copy link

t3hmrman commented Aug 30, 2018

Hey @resouer to make sure I clearly understand, which of these are right:

  • Frakti v2 will be a containerd plugin (similar to how cri-containerd is now a in-tree plugin)
  • Frakti v2 will be rolled into the kata-containers

Those two facts seem at odds, because containerd already has an untrusted workload runtime option (on which you could set kata-runtime to run your untrusted workloads) -- Also, it doesn't really make sense for Frakti to merge into kata-runtime because Frakti is supposed to be able to handle both untrusted and trusted runtimes.

Is there somewhere I could read a bit more about how the project is moving? I'm helicoptering by and not watching closely but if there's some mailing list or forum I could read I'll go do that.

@resouer

This comment has been minimized.

Copy link
Member

resouer commented Aug 31, 2018

Hi @t3hmrman, not sure if you have read the RuntimeClass proposal? See: https://github.com/kubernetes/community/blob/master/keps/sig-node/0014-runtime-class.md

It's exactly where we are going. The trusted/untrusted annotations will be deprecated, and frakti v2 will only include several containerd focus plugins to handle runtimes, networking, and storage. And of course, a doc about how to set these pieces up to serve as a production ready runtime for Kubernetes.

@t3hmrman

This comment has been minimized.

Copy link

t3hmrman commented Aug 31, 2018

hey @resouer Thanks so much for the pointer, I haven't actually seen the RuntimeClass proposal at all.

That makes total sense, frakti becoming a well-integrated containerd plugin sounds great -- I'm a huge fan of containerd (+ cri-containerd, the intergration was pretty smooth for them).

Thanks for taking the time to explain!

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Sep 30, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot

This comment has been minimized.

Copy link

k8s-ci-robot commented Sep 30, 2018

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment