We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the best way to document out API? Once we have swagger spec, I think we can get some documentation for free. In the mean time: https://github.com/kubernetes/kops/blob/master/docs/cluster_spec.md <- out of date
The text was updated successfully, but these errors were encountered:
This needs to be pulled from code..
Also this brings up the question of versioning our documentation #1583
Sorry, something went wrong.
Follow up thought..
what if the API machinery could generate docs based on API versions..
K8s is generating this https://kubernetes.io/docs/api-reference/v1.5/ <- we need to figure out how to
Closing this and opening another issue about using the API server to generate docs.
No branches or pull requests
What is the best way to document out API? Once we have swagger spec, I think we can get some documentation for free. In the mean time: https://github.com/kubernetes/kops/blob/master/docs/cluster_spec.md <- out of date
The text was updated successfully, but these errors were encountered: