feat(platform): introduce Platform API at v1alpha1 level

[tylerslaton]

Summary

Adding the necassary API's for PlatformOperators as outlined by this EP. This is a work in progress PR that is meant to burn down on review while the EP finishes up and is thus subject to change as progress is made. This PR is now ready for review.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

Hello @tylerslaton! 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 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

[tylerslaton]

/test all

[tylerslaton]

/test all

[timflannagan]

@tylerslaton Once we get the CRD generation working, we need to ensure that the release.openshift.io/feature-gate: "TechPreviewNoUpgrade" k/v annotation is present on that manifest.

[tylerslaton]

/retest

[tylerslaton]

/retest

[timflannagan]

cc @joelanford

[joelanford]

In case it isn't clear, it should be noted that the EP for platform operators dictates that the PlatformOperator.metadata.name is the only input necessary for reconciliation, for now at least.

That value will be interpreted as the package name that the controller should lookup and attempt to source bundles from.

[timflannagan]

/lgtm

[timflannagan]

Wow crazy timing.

/lgtm cancel

[openshift-ci]

@tylerslaton: all tests passed!

Full PR test history. Your PR dashboard.

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

[JoelSpeed]

/lgtm

[tylerslaton]

@jianzhangbjz @michaelryanpeter Would you mind taking a look and giving the QE/Doc tags here?

[deads2k]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, JoelSpeed, tylerslaton

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

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

[jianzhangbjz]

/label qe-approved

[adellape]

/label docs-approved

[sferich888]

/label px-approved