-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Update cloning docs to reflect beta for 1.16 #16013
Update cloning docs to reflect beta for 1.16 #16013
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 7effc78 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5d6a7fc210bca20007a71f76 |
feature-gates.md also needs to be updated |
e039d18
to
a38d7fc
Compare
@@ -174,7 +174,7 @@ different Kubernetes components. | |||
| `TokenRequestProjection` | `false` | Alpha | 1.11 | 1.11 | | |||
| `TokenRequestProjection` | `true` | Beta | 1.12 | | | |||
| `TTLAfterFinished` | `false` | Alpha | 1.12 | | | |||
| `VolumePVCDataSource` | `false` | Alpha | 1.15 | | | |||
| `VolumePVCDataSource` | `true` | Beta | 1.16 | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we add a new line for beta and keep the alpha entry
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh shoot, you're right fixed.
a38d7fc
to
0f12dab
Compare
@@ -175,6 +175,7 @@ different Kubernetes components. | |||
| `TokenRequestProjection` | `true` | Beta | 1.12 | | | |||
| `TTLAfterFinished` | `false` | Alpha | 1.12 | | | |||
| `VolumePVCDataSource` | `false` | Alpha | 1.15 | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And the "Until" column needs to be updated too :-)
0f12dab
to
6671661
Compare
@@ -174,7 +174,8 @@ different Kubernetes components. | |||
| `TokenRequestProjection` | `false` | Alpha | 1.11 | 1.11 | | |||
| `TokenRequestProjection` | `true` | Beta | 1.12 | | | |||
| `TTLAfterFinished` | `false` | Alpha | 1.12 | | | |||
| `VolumePVCDataSource` | `false` | Alpha | 1.15 | | | |||
| `VolumePVCDataSource` | `false` | Alpha | 1.15 | 1.16 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I think it's inclusive, so should be 1.15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, my fault completely, thanks for keeping me honest when I'm rushing.
6671661
to
78c5bde
Compare
@j-griffith is this tied to any enhancement? |
/lgtm |
/milestone 1.16 |
@simplytunde Yes, associated with update of KEP (merged): PR for the feature itself is here: kubernetes/kubernetes#81792 |
/hold cancel |
@@ -32,7 +32,7 @@ The {{< glossary_tooltip text="CSI" term_id="csi" >}} Volume Cloning feature add | |||
|
|||
A Clone is defined as a duplicate of an existing Kubernetes Volume that can be consumed as any standard Volume would be. The only difference is that upon provisioning, rather than creating a "new" empty Volume, the back end device creates an exact duplicate of the specified Volume. | |||
|
|||
The implementation of cloning, from the perspective of the Kubernetes API simply adds the ability to specify an existing unbound PVC as a dataSource during new pvc creation. | |||
The implementation of cloning, from the perspective of the Kubernetes API simply adds the ability to specify an existing unbound PVC as a dataSource during new pvc creation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PVC example below doesn't specify a storageclass, but we made it required right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
StorageClass is not actually required, it's just required that the source and destination are in the same storageClass. This can either be specified via storageClassName or by having a default storageClass.
I updated the doc to try and clarify that.
/lgtm cancel |
Updates the feature status for VolumePVCDataSource to 1.16/beta in the docs.
78c5bde
to
7effc78
Compare
/lgtm |
/milestone clear |
@j-griffith looks like the enhancement will be in 1.16. can you close this? |
Confused, this should be in 1.16 right? We're waiting on docs to give a final review/approval |
sorry about that. Yes, it is still going into 1.16 |
/milestone 1.16 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: simplytunde The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Updates the feature status for VolumePVCDataSource to 1.16/beta in the
docs.
Associated KEP update: kubernetes/enhancements#1147