Snapshot Support for Kubernetes (CRD + External Controller)

[xing-yang]

Feature Description

• One-line feature description (can be used as a release note): Snapshot/restore functionality for Kubernetes and CSI. This provides standardized APIs design (CRDs) and adds PV snapshot/restore support for CSI volume drivers.
• Primary contact (assignee): @jingxu97 @xing-yang
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): CSI snapshot design community#2335
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @saad-ali
  @jsafrane
• Approver (likely from SIG/area to which feature belongs):
  @thockin
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.12
  • Beta release target (x.y): 1.13
  • Stable release target (x.y): 1.14

[k8s-ci-robot]

@xing-yang: Reiterating the mentions to trigger a notification:
@kubernetes/sig-storage-feature-requests

In response to this:

Feature Description

• One-line feature description (can be used as a release note): Move snapshot support in-tree.
• Primary contact (assignee): @jingxu97 @xing-yang
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): Add Volume Snapshot Support Proposal community#1624
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @saad-ali
  @jsafrane
• Approver (likely from SIG/area to which feature belongs):
  @thockin
• Feature target (which target equals to which milestone):
• Alpha release target (x.y): 1.10
• Beta release target (x.y): 1.11
• Stable release target (x.y): 1.12

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.

[xing-yang]

@kubernetes/sig-storage-feature-requests

[k8s-ci-robot]

@xing-yang: Reiterating the mentions to trigger a notification:
@kubernetes/sig-storage-feature-requests

In response to this:

@kubernetes/sig-storage-feature-requests

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.

[idvoretskyi]

/assign @jingxu97 @xing-yang

[saad-ali]

We're moving this to 1.11. For this quarter the focus is on coming up with a Restore API and CSI implementation (both out-of-tree)

[mlmhl]

Do we have any plan for this feature in 1.11? @saad-ali @jingxu97 @xing-yang

[xing-yang]

@mlmhl We'll discuss about it in today's sig-storage planning meeting and make a decision.

[xing-yang]

@mlmhl We have agreed to work on this and target for 1.11 Alpha.

[mlmhl]

Thanks @xing-yang . My team is very looking forward to this feature, and I can help to move along this feature if you needed.

[xing-yang]

Thanks @mlmhl! I'll keep that in mind.

[idvoretskyi]

@xing-yang @saad-ali @kubernetes/sig-storage-feature-requests can you confirm that this feature is planned for 1.11?

/cc @justaugustus

[xing-yang]

@idvoretskyi Yes, we are targeting this feature for 1.11.

[mdlinville]

@xing-yang @jingxu97 please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

[xing-yang]

@MistyHacks We are delaying this to 1.12. Thanks.

[mdlinville]

@justaugustus @idvoretskyi FYI

[justaugustus]

@xing-yang @jingxu97 @kubernetes/sig-storage-feature-requests --

This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38

[tpepper]

Is this still targeting 1.12, or does moving to CRD slow and put the implementation at risk?

[xing-yang]

@tpepper @justaugustus Yes, this is still targeting 1.12. Thanks.

[justaugustus]

Thanks for the update! This has been added to the 1.12 Tracking sheet.

[saad-ali]

Looks like this is a duplicate of #177

Closing this issue. Please put further updates on #177