Annotate manifests for single-node-developer cluster profile

[rkukura]

This partially implements phase 1 of openshift/enhancements#482 and
does not change behavior. Initially, all API CRD manifests are
included in the single-node-developer cluster profile. Follow-on PRs
may exclude any of these that are not needed in the profile.

[openshift-ci-robot]

Hi @rkukura. Thanks for your PR.

I'm waiting for a openshift 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.

Details

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.

[cfergeau]

/ok-to-test

[sttts]

This implements the annotation described in the approved enhancement.

/lgtm
/approve

@rkukura note, that you have to bump a large number of operators to pick these changes up. The api repo alone does not ship these changes.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rkukura, sttts

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sttts]

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

[sttts]

/retest