-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Proposal for minikube tips #11696
Proposal for minikube tips #11696
Conversation
Signed-off-by: Peixuan Ding <dingpeixuan911@gmail.com>
Hi @dinever. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Can one of the admins verify this patch? |
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 like this proposal - simple, clean, good. Very well done!
|
||
1. Is there a more preferred file format to YAML? | ||
|
||
2. Maybe we just want to sync the tips to the `FAQ` page list instead of creating a new page? |
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 the original plan was to sync with FAQ but I think new page is the way to go, FAQ should be specifically for answering questions to common problems, tips should be interesting features people might want to try out.
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.
Thanks for the feedback @andriyDev! Yep it's kind of hard to fit these tips with the current FAQ items. Will bring this up in office hour and see what everyone thinks.
``` | ||
``` | ||
|
||
On the docs side we should both questions and answers. On the CLI side |
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.
Interesting idea! I think wording that correctly can be very tricky though, so it makes sense as a tip and as an answer. I'm a much bigger fan of just a set of tips.
|
||
## Alternatives Considered | ||
|
||
1. Is there a more preferred file format to YAML? |
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 only other file format we might use is JSON, and while I do like the JSON structure, it has a big flaw which is that new lines must be replaced with \n which can get messy, and make it hard to see how the tip actually looks. I'm pretty happy with YAML for the file format because it makes it very clear how it looks.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: andriyDev, dinever The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi,
This is a proposal for #11207. Would like to collect some feedback before submitting any PRs.
Thanks!