-
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
Add docs about VolumeAttributesClass API (KEP-3751) #43463
Add docs about VolumeAttributesClass API (KEP-3751) #43463
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
/retitle [WIP] Add post-release blog article about VolumeAttributesClass KEP-3751 /hold |
@sftim The instruction link I got says create an PR against dev-1.29, it this not the case anymore? Can you send me the correct documentaion? |
You can turn this into a documentation PR, in which case the branch is right but the path is wrong: change Right now this has a mismatch because it changes a blog path. PRs that add blog articles never go on release branches. |
@sftim which folder under docs I should post for a new feature? The structure is not clear to me. Does concepts/storage make sense? |
1a6c401
to
3a16a18
Compare
@sunnylovestiramisu I think you just need to rename the title of this PR. It says "Add post-release blog article about VolumeAttributesClass KEP-3751". Just change that to "Add doc about VolumeAttributesClass KEP-3751". |
It looks like "area/blog" label was added by the bot automatically probably because "blog" is in the PR title. /area blog cancel |
@xing-yang: The label(s) In response to this:
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. |
/remove-area blog |
/retitle [WIP] Add docs about VolumeAttributesClass API (KEP-3751) |
2809a5c
to
03bc782
Compare
/lgtm |
LGTM label has been added. Git tree hash: fd3e6d8eadcff001adcda87c1fd20d30ecd02009
|
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.
/lgtm
/approve
Thanks @sunnylovestiramisu for the hard work on this!
03bc782
to
ba6f6c3
Compare
/lgtm |
LGTM label has been added. Git tree hash: c00480cfffdfba536a910b64a70bb96cc0de4438
|
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.
Some more feedback
If you want to test the feature whilst it's alpha, you need to enable the relevant feature gate | ||
in the kube-controller-manager and the kube-apiserver. Use the --feature-gates command line argument: |
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.
If you want to test the feature whilst it's alpha, you need to enable the relevant feature gate | |
in the kube-controller-manager and the kube-apiserver. Use the --feature-gates command line argument: | |
If you want to test the feature whilst it's alpha, you need to enable the `VolumeAttributesClass` | |
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kube-controller-manager and the kube-apiserver. You use the `--feature-gates` command line argument: |
--feature-gates="...,VolumeAttributesClass=true" | ||
``` | ||
|
||
It also requires the CSI driver has implemented the ModifyVolume API. |
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.
It also requires the CSI driver has implemented the ModifyVolume API. | |
You can also only use VolumeAttributesClasses with storage backed by | |
{{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}}, and only where the | |
relevant CSI driver implements the `ModifyVolume` API. |
@@ -816,6 +817,7 @@ Each feature gate is designed for enabling/disabling a specific feature: | |||
support for CEL validations be used in Admission Control. | |||
- `VolumeCapacityPriority`: Enable support for prioritizing nodes in different | |||
topologies based on available PV capacity. | |||
- `VolumeAttributesClass`: Enable support for VolumeAttributesClass |
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.
(nit)
- `VolumeAttributesClass`: Enable support for VolumeAttributesClass | |
- `VolumeAttributesClass`: Enable support for VolumeAttributesClasses. | |
See [Volume Attributes Classes](/docs/concepts/storage/volume-attributes-classes/) | |
for more information. |
/approve This PR already exceeds our docs quality expectations for alpha features. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saad-ali, sftim 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 |
ba6f6c3
to
058e522
Compare
/lgtm |
LGTM label has been added. Git tree hash: 0f3550578724c8ccacc8d0ed8f8a6451b9a951f4
|
Great work today!! As a frequent reader of the Kubernetes docs, thank you for your quality contribution 😄 |
kubernetes/enhancements#3751
kubernetes/kubernetes#121104
Doc draft in Google doc