diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-09-03 09:11:19 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-09-03 09:11:19 -0700 |
| commit | cf50de734257b81788bc65701fe49424997197f3 (patch) | |
| tree | 36affd53a356879456ea4e6b28e5940089530c97 /scripts | |
| parent | f1f7f2e6f42e198ac7c8d1257068dddc14b01aad (diff) | |
| parent | 672de53afe31f18f5edbe4d0e97d88eea3c9c333 (diff) | |
Merge pull request #31919 from ciwang/designdoc
Automatic merge from submit-queue
Snapshotting design doc
<!-- Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->
**What this PR does / why we need it**:
Design doc for volume snapshotting feature (alpha)
**Special notes for your reviewer**:
**Release note**:
<!-- Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access)
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`.
-->
```release-note
```
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
