Closed biwenKey closed 3 years ago
The core v1 API group is huge for legacy reason. The doc is generated from the upstream openapi spec by the openapi-generator. I think the issue applies to all the generated clients (e.g. the java client) as well. You could download the raw file and view it with a different render that supports larger files than Github
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Until the issue is fixed, this might help some people. Written for complete newbies so no one should have problems with it (if you use *nix)
Required tools:
mkdir -p html
for source in *.md; do
[ -f "$source" ] || break
output=${source/.md/.html}
pandoc -s \
-t html \
-o html/$output \
-f gfm \
--template mindoc-pandoc.html \
--metadata title=`basename $source` \
$source
sed -i 's/.md/.html/g' html/$output
done
Usage:
cd kubernetes/docs
wget https://raw.githubusercontent.com/bitfragment/mindoc/master/dist/mindoc-pandoc.html
or curl https://raw.githubusercontent.com/bitfragment/mindoc/master/dist/mindoc-pandoc.html
html
directory with docs that have working links (except for README.md as I didnt care about it, feel free to adjust it to include it)xdg-open html/CoreV1Api.html
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
Link to the issue (please include a link to the specific documentation or example):
Description of the issue (please include outputs or screenshots if possible):