NE-1303: cluster version: add v4.16 set and ingress capability

[alebedev87]

Retake of #1516.

Enhancement Proposal: openshift/enhancements#1415.

This PR introduces a new Ingress cluster capability which allows to enable or disable the default ingress of the OpenShift cluster: the cluster ingress operator and its custom resources. The Ingress capability is added to a new 4.16 capabilityset as it's the first capability added for 4.16. The two CRDs managed by the cluster ingress operator are annotated with Ingress capability: IngressController, DNSRecord.

[openshift-ci]

Hello @alebedev87! 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.

[openshift-ci-robot]

@alebedev87: This pull request references NE-1303 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Retake of #1516.

Enhancement Proposal: openshift/enhancements#1415.

This PR introduces a new Ingress cluster capability which allows to enable or disable the default ingress of the OpenShift cluster: the cluster ingress operator and its custom resources. The Ingress capability is added to a new 4.16 capabilityset as it's the first capability added for 4.16. The two CRDs managed by the cluster ingress operator are annotated with Ingress capability: IngressController, DNSRecord.

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 openshift-eng/jira-lifecycle-plugin repository.

[alebedev87]

/test e2e-gcp

[bparees]

/approve

[alebedev87]

Rebased to fix the conflicts with master.

[alebedev87]

/assign @Miciah

[Miciah]

Thanks!
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87, bparees, Miciah

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

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

[openshift-ci]

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

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-api-container-v4.16.0-202402130340.p0.g06532f4.assembly.stream.el9 for distgit ose-cluster-config-api.
All builds following this will include this PR.