Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/tadayosi/gen-crd-api-reference-docs

API Reference Docs generator for Kubernetes CRDs (used by Knative, Kubeflow and others)
https://github.com/tadayosi/gen-crd-api-reference-docs

Last synced: 3 days ago
JSON representation

API Reference Docs generator for Kubernetes CRDs (used by Knative, Kubeflow and others)

Awesome Lists containing this project

README 

        
# Kubernetes Custom Resource API Reference Docs generator



If you have a project that is Custom Resource Definitions and wanted to generate

API Reference Docs [like this][ar] this tool is for you.



[ar]: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/



## Current Users



- [**Knative** API reference docs](https://knative.dev/docs/reference/api/serving-api/)

- [**Kubeflow** API reference docs](https://www.kubeflow.org/docs/reference/overview/)

- [**Agones** API reference docs](https://agones.dev/site/docs/reference/agones_crd_api_reference/)

- [**cert-manager** API reference docs](https://cert-manager.io/docs/reference/api-docs/)

- [**Gardener** API reference docs](https://gardener.cloud/api-reference/)

- [**New Relic Alert Manager** API reference docs](https://github.com/fpetkovski/newrelic-alert-manager/tree/master/docs)

- _[[ADD YOUR PROJECT HERE]]_



## Why



Normally you would want to use the same [docs generator][dg] as [Kubernetes API

reference][ar], but here's why I wrote a different parser/generator:



1. Today, Kubernetes API [does not][pr] provide OpenAPI specs for CRDs (e.g.

   Knative), therefore the [gen-apidocs][ga]

   generator used by Kubernetes won't work.



2. Even when Kubernetes API starts providing OpenAPI specs for CRDs, your CRD

   must have a validation schema (e.g. Knative API doesn't!)



3. Kubernetes [gen-apidocs][ga] parser relies on running a `kube-apiserver` and

   calling `/apis` endpoint to get OpenAPI specs to generate docs. **This tool

   doesn't need that!**



[dg]: https://github.com/kubernetes-incubator/reference-docs/

[ga]: https://github.com/kubernetes-incubator/reference-docs/tree/master/gen-apidocs/generators

[pr]: https://github.com/kubernetes/kubernetes/pull/71192



## How



This is a custom API reference docs generator that uses the

[k8s.io/gengo](https://godoc.org/k8s.io/gengo) project to parse types and

generate API documentation from it.



Capabilities of this tool include:



- Doesn't depend on OpenAPI specs, or kube-apiserver, or a running cluster.

- Relies only on the Go source code (pkg/apis/**/*.go) to parse API types.

- Can link to other sites for external APIs. For example, if your types have a

  reference to Kubernetes core/v1.PodSpec, you can link to it.

- [Configurable](./example-config.json) settings to hide certain fields or types

  entirely from the generated output.

- Either output to a file or start a live http-server (for rapid iteration).

- Supports markdown rendering from godoc type, package and field comments.



## Try it out



1. Clone this repository.



2. Make sure you have go1.11+ instaled. Then run `go build`, you should get a

   `gen-crd-api-reference-docs` binary executable in the current directory.



3. Clone a Knative repository, set GOPATH correctly,

   and call the compiled binary within that directory.



    ```sh

    # go into a repository root with GOPATH set. (I use my own script

    # goclone(1) to have a separate GOPATH for each repo I clone.)

    $ goclone knative/build



    $ /path/to/gen-crd-api-reference-docs \

        -config "/path/to/example-config.json" \

        -api-dir "github.com/knative/build/pkg/apis/build/v1alpha1" \

        -out-file docs.html

    ```



4. Visit `docs.html` to view the results.



-----



This is not an official Google project. See [LICENSE](./LICENSE).