-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Move wiki documents under @docs/` and update them #4008
Comments
Once the docs are moved we should also update docs button on Done in #4052. |
We should close the Wikis once this will be done. |
Arch image should be updated to replace Heapster. |
Please also add #3504 (comment) info to the docs. Can be placed in FAQ or some dev doc. Notice that YAML location changed and add also URL to enter the app. |
@jeefy Would be nice if you would describe dev process with the metrics. Some manual, tips etc. |
|
/assign |
it would be done in #4169. |
Done in #4169 |
@maciaszczykm @jeefy I'm unlikely to be able to update FAQ, Roadmap and Integrations well. Could you guys update them? |
For FAQ, it's worth to mention that |
For FAQ, it's worth to describe increasing kernel setting To increase the parameter, run |
These updates are creating broken links support sites, including the issues in this project. Is there a way to redirect from the wiki to the new address? For example, going to https://github.com/kubernetes/dashboard/wiki/Creating-sample-user now redirects to the wiki home page. And from what I'm reading in this issue, soon all documentation links will do the same. Here are two examples of where this issue is occuring: |
Also #4121 should be covered by this issue. |
Wiki contents that should be migrated to |
Reasons
TODOs
2.0.0 or later
docs/
, create indexes and blank pages. Reorganizedocs/
#40091.10.1 or before
After migration to
docs/
, revert wiki for <=1.10.1.<=1.10.1
on wiki pages. (maintainer only)docs/
for>=2.0.0
" on wiki pages. (maintainer only)<=1.10.1
later.Old documents are all removed.
The text was updated successfully, but these errors were encountered: