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
Document generic data sources feature #19315
Document generic data sources feature #19315
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit 1a3853a https://deploy-preview-19315--kubernetes-io-master-staging.netlify.com |
c57f95f
to
f43d7e9
Compare
/assign @msau42 |
Link to the relevant section of the preview: |
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.
Also add the feature gate to https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates
|
||
Users may create their own data populator CRDs and write their own data populator controllers | ||
to handle them. Such data populators are responsible for creating the persistent volume and | ||
binding it to the PVC on their own. |
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.
This can be easily messed up and has been the cause of some security vulnerabilities in the past. Do we intend to have an example that people can follow?
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 have the hello-populator example from the original KEP. The plan was to present a formal design for how this should work and to get that approved as part of graduation to beta.
While writing these docs I realized how particularly unhelpful it is to have a feature gate with so little to say about it. Before beta we also need to address the issue of how users can find out what populators exist, and making sure to return good error messages when someone attempts to use something that's not installed.
Do you think it's better to say less? I don't want to encourage people to write code that will cause security problems.
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.
Yeah maybe until we have agreed upon pattern for populators we should not add a section here. Instead just document the feature gate.
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 removed this section and instead just documented the feature gate.
f43d7e9
to
1d59eb2
Compare
/lgtm |
Hi @bswartz Thanks! |
This is ready to merge. Just waiting for approval. |
@bswartz please target the /cc @VineethReddy02 @zacharysarah |
@msau42 PR rebased on dev-1.18 |
@bswartz I think you'll need to change the base branch for this PR to dev-1.18; it's currently master. For safety, I'm going to add a Happy to run through details in case this is supposed to merge into master. https://kubernetes.io/docs/contribute/start/#choose-which-git-branch-to-use explains how SIG Docs uses branches. |
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.
Markdown looks good to me.
If you're revising: here's an optional tweak you can make.
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
…-gates.md Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 500c8e4 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5e6ffe2325406d0008790b1d |
@sftim Thank you! |
/remove- area blog |
/remove-area blog |
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
Hey @bswartz , The changes look okay. I assume that this feature is a new addition for 1.18 or are you documenting an existing Alpha feature? Typically, there should be docs to introduce the feature. |
@kbhawkey We decided to skip that for this feature since it's mostly developer facing (until beta) and any user-facing explanations would probably cause more problems then help. Earlier on I had a few paragraphs in the storage section, but I removed them after discussion with @msau42 . |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: VineethReddy02 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 |
Document the AnyVolumeDataSource feature gate. Don't include any user-facing documentation at this time, because the the feature is experimental and only relevant to developers.