Skip to content

Conversation

@alebedev87
Copy link
Contributor

Delete all unmanaged Gateway API CRDs present in the cluster. An unmanaged Gateway API CRD is one with gateway.networking.k8s.io or gateway.networking.x-k8s.io in its spec.group field, and not managed by the gatewayapi controller.

Delete all unmanaged Gateway API CRDs present in the cluster.
An unmanaged Gateway API CRD is one with "gateway.networking.k8s.io" or
"gateway.networking.x-k8s.io" in its "spec.group" field,
and not managed by the gatewayapi controller.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 21, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 21, 2025

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

In response to this:

Delete all unmanaged Gateway API CRDs present in the cluster. An unmanaged Gateway API CRD is one with gateway.networking.k8s.io or gateway.networking.x-k8s.io in its spec.group field, and not managed by the gatewayapi controller.

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.

@openshift-ci openshift-ci bot requested review from candita and rfredette March 21, 2025 16:40
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2025

@alebedev87: 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/hypershift-e2e-aks 5bb7600 link true /test hypershift-e2e-aks
ci/prow/e2e-hypershift 5bb7600 link true /test e2e-hypershift
ci/prow/e2e-aws-operator-techpreview 5bb7600 link false /test e2e-aws-operator-techpreview
ci/prow/e2e-aws-ovn-single-node 5bb7600 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-gatewayapi 5bb7600 link false /test e2e-aws-gatewayapi
ci/prow/e2e-aws-ovn-techpreview 5bb7600 link false /test e2e-aws-ovn-techpreview

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.

@alebedev87
Copy link
Contributor Author

/hold

The unmanaged Gateway API CRDs will be handled via a Degraded cluster operator. Holding to close until the PR which takes over is posted.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2025
@alebedev87
Copy link
Contributor Author

Closing in favor of #1205.

@alebedev87 alebedev87 closed this Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants