[OCPNODE-521]Register ImageDigest/TagMirrorSet CRDs

[QiWang19]

Register ImageDigestMirrorset, ImageTagMirrorSet from 4.13.
These CRDs were unregistered before since we planned it for 4.13. Now, 4.13 branch is open, we can get this in.

CRD implementation: openshift/machine-config-operator#3037

[openshift-ci]

Hello @QiWang19! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard lgtm and approved labels this repository requires either:

bugzilla/valid-bug - applied if your PR references a valid bugzilla bug

OR

qe-approved, docs-approved, and px-approved - these labels can be applied by anyone in the openshift org via the /label <labelname> command.

Who should apply these qe/docs/px labels?

• For a no-Feature-Freeze team who is merging a feature before code freeze, they need to get those labels applied to their api repo PR by the appropriate teams (i.e. qe, docs, px)
• For a Feature Freeze (traditional) team who is merging a feature before FF, they can self-apply the labels (via /label commands), they are basically irrelevant for those teams
• For a Feature Freeze team who is merging a feature after FF, the PR should be rejected barring an exception

[QiWang19]

/label px-approved
/label qe-approved
/label docs-approved

[QiWang19]

/hold

4.13 tree to open

[QiWang19]

/hold cancel
4.13 branch is open

[rphillips]

/lgtm
/assign @JoelSpeed

[QiWang19]

@deads2k Could you merge this? the CRDs was unregistered before #1296 since we planned it for 4.13

[JoelSpeed]

/test all

[JoelSpeed]

You need to add integration tests for these CRDs to pass, please checkout the repo, rebase on the latest changes and run ./tests/hack/gen-minimal-test.sh ./config/v1 v1 and it should generate a minimal test for both CRDs. Make sure these pass (make -C config/v1 test), and if they don't, that means you have required or defaulted fields, add these to the minimal tests as appropriate

[openshift-ci]

@QiWang19: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[QiWang19]

@JoelSpeed @rphillips PTAL

[JoelSpeed]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, QiWang19, rphillips

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 [JoelSpeed]

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