feature-flags: Create a feature flag for Platform Operators Tech Preview

[exdx]

Adds a new feature flag for the Platform Operators Openshift-only feature.

Signed-off-by: Daniel Sover dsover@redhat.com

[openshift-ci]

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

[timflannagan]

Link to the EP that proposes introducing this feature flag: openshift/enhancements#1170. Note: that EP still hasn't been approved yet.

cc @bparees @joelanford

[openshift-ci]

@exdx: 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.

[michaelryanpeter]

/label docs-approved

[jianzhangbjz]

/label qe-approved

[tylerslaton]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: exdx, tylerslaton
Once this PR has been reviewed and has the lgtm label, please assign derekwaynecarr for approval by writing /assign @derekwaynecarr in a comment. For more information see:The Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[exdx]

/hold

It's unclear whether this is actually required for PO Phase 0, and what the response from PX will be.

[joelanford]

^ +1 to the hold.

Since the entire PO system will be tech preview for phase 0, I think we're planning to use CVO's release.openshift.io/feature-gate: "TechPreviewNoUpgrade" annotation support in the PO manifests.

[exdx]

Closing as this is not required for PO Phase 0.