Enhancements: Containerd CRI Integration

Created on 29 Apr 2017  Â·  18Comments  Â·  Source: kubernetes/enhancements

Feature Name

  • One-line feature description (can be used as a release note): Alpha containerd CRI integration with basic sandbox/container lifecycle management and image management.
  • Primary contact (assignee): @Random-Liu
  • Responsible SIGs: sig-node
  • Design proposal link (community repo): https://github.com/kubernetes-incubator/cri-containerd/blob/master/docs/proposal.md
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @mikebrow @yujuhong
  • Approver (likely from SIG/area to which feature belongs): @dchen1107
  • Feature target (which target equals to which milestone): alpha 1.7
kinfeature sinode stagstable

Most helpful comment

Status Update

All 18 comments

@Random-Liu it seems to be a notable feature - any documentation can be provided? /cc @dchen1107 @kubernetes/sig-node-feature-requests

@idvoretskyi Hi, the document will be located in the cri-containerd repo.

We'll add document to k8s.io next release with feature complete.

Thanks

On Tue, Jun 20, 2017, 6:45 PM Lantao Liu notifications@github.com wrote:

@idvoretskyi https://github.com/idvoretskyi Hi, the document will be
located in the cri-containerd
https://github.com/kubernetes-incubator/cri-containerd repo.

We'll add document to k8s.io next release with feature complete.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/286#issuecomment-309818616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHOu-xWSnUxVn2OwzGe9uyXaZxCJjZ1ks5sF_cZgaJpZM4NMGSa
.

@Random-Liu @kubernetes/sig-node-feature-requests any progress for 1.8?

If yes, please, update the features tracking board with the relevant data.

1.0-alpha planned for release at the end of September

Status Update

thanks for the update, @Random-Liu

@Random-Liu can you update the features tracking board with the relevant data?

Thanks.

@idvoretskyi Will do. Thanks for reminding!

@idvoretskyi Done

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

/remove-lifecycle stale

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

@Random-Liu
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:

    • stage/{alpha,beta,stable}

    • sig/*

    • kind/feature

cc @idvoretskyi

/remove-lifecycle stale

@Random-Liu @mikebrow pinging again for status.

Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:

    • stage/{alpha,beta,stable}

    • sig/*

    • kind/feature

The feature is GA now.

Status Update

Thanks for the update, @Random-Liu!
I'll go ahead and close this out.

/remove-help
/close

Was this page helpful?
0 / 5 - 0 ratings

Related issues

andrewsykim picture andrewsykim  Â·  12Comments

liggitt picture liggitt  Â·  7Comments

justaugustus picture justaugustus  Â·  3Comments

AndiLi99 picture AndiLi99  Â·  13Comments

prameshj picture prameshj  Â·  9Comments