Document root CRD objects as API resource types.

[jpeach]

When finding the set of root CRD types, the documentation
generator checks for the +genclient annotation, ratherd
than the newer +kubebuilder:object:root.

Adding +genclient makes the root CRD type objects appear in the
resource list at the head of the API documentation, which improves
their visibility.

Signed-off-by: James Peach jpeach@vmware.com

[k8s-ci-robot]

Hi @jpeach. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jpeach]

xref ahmetb/gen-crd-api-reference-docs#15

[jpeach]

@robscott Can you PTAL at your leisure?

[robscott]

Thanks! This is a nice addition. For anyone curious, in addition to moving all the top level resources to the top, it adds some helpful top-level links to them.

/ok-to-test
/lgtm

[bowei]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, jpeach

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [bowei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment