NE-1871: Promote GatewayAPI to Tech Preview

[rfredette]

Enhancement: Gateway API with Cluster Ingress Operator

[openshift-ci]

Hello @rfredette! 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rfredette
Once this PR has been reviewed and has the lgtm label, please assign derekwaynecarr for approval. 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

[openshift-ci-robot]

@rfredette: This pull request references NE-1871 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.18.0" version, but no target version was set.

In response to this:

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.

[rfredette]

test failures seem unrelated
/retest

[openshift-ci-robot]

@rfredette: This pull request references NE-1871 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.18.0" version, but no target version was set.

In response to this:

Enhancement: Gateway API with Cluster Ingress Operator

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.

[rfredette]

/jira refresh

[openshift-ci-robot]

@rfredette: This pull request references NE-1871 which is a valid jira issue.

In response to this:

/jira refresh

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.

[rfredette]

Until the Gateway API feature is ready to be considered tech preview:
/hold

[candita]

/assign @gcs278
/assign @Thealisyed

[candita]

@gcs278 @rfredette based on our team meeting this morning, we would like to pursue merging this so Gateway API integration can get the CI exercise that a TechPreview cluster gets, on all platforms. Can you please unhold and review so we can make that happen?

[gcs278]

@gcs278 @rfredette based on our team meeting this morning, we would like to pursue merging this so Gateway API integration can get the CI exercise that a TechPreview cluster gets, on all platforms. Can you please unhold and review so we can make that happen?

@candita maybe I misunderstood, but I thought the decision was to wait until 4.19 branch opens to bump the feature gate to Tech Preview. In 4.19, we'd would do Dev Preview --> Tech Preview --> GA, all in the same development cycle.

[candita]

@gcs278 @rfredette based on our team meeting this morning, we would like to pursue merging this so Gateway API integration can get the CI exercise that a TechPreview cluster gets, on all platforms. Can you please unhold and review so we can make that happen?

@candita maybe I misunderstood, but I thought the decision was to wait until 4.19 branch opens to bump the feature gate to Tech Preview. In 4.19, we'd would do Dev Preview --> Tech Preview --> GA, all in the same development cycle.

No, it's better for us to do this without having to backport it after branch cut if possible.

[openshift-ci]

@rfredette: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-hypershift	b9afb68	link	true	/test e2e-aws-ovn-hypershift
ci/prow/lint	b9afb68	link	true	/test lint

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

[openshift-merge-robot]

PR needs rebase.

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-sigs/prow repository.

[gcs278]

@candita @rfredette I think we are ready to proceed with this PR now that 4.18 branch cut has happened based on our conversation in slack. We'll have to wait until after the holidays to merge, but following up here before I forget.