-
Notifications
You must be signed in to change notification settings - Fork 823
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
Documentation for the extended Kubernetes API #409
Comments
This is currently blocked by: kubernetes-sigs/kubebuilder#483 Will wait for it to get fixed. |
Another tool to try out: https://github.com/ahmetb/gen-crd-api-reference-docs (this looks way more promising) |
Any interest? I can help you get this done in ~20 minutes. |
Yep, definitely! Just haven't got to it yet! Will need to integrate it into our build image, and our Make targets so we can regenerate on model change though! |
I see that Kubebuilder has an issue and functionality "Generate docs" seems to be not supported yet. |
Yeah, if there is a way we can integrate this into agones.dev somehow, I think that would be ideal 👍 Maybe whenever we run |
I need to investigate more on how generated docs would look like and how to integrate them into |
@aLekSer can we close this now? |
Whoops - hit the wrong button, but @aLekSer should we reopon this? |
Agree with closing that, I think the main part is done, the rest is to polish current version, only some small warnings while parsing "./pkg/apis/stable/v1alpha1/" occurred:
|
Yeah we can probably make them lower level logs instead of warnings. If they bother you, feel free to make small PR to the generator! |
When we implement CRDs for Agones, we create new API endpoints for each CRD.
It would be great to document these, and publish it somewhere, so that people can more easily integrate, and we can reference it in our documentation.
I feel there are several steps:
make
target that generates the documentationResources
The text was updated successfully, but these errors were encountered: