Skip to content

Conversation

@rikatz
Copy link
Member

@rikatz rikatz commented Oct 21, 2025

This enhancement proposal adds the Ingress Controller Conditions (LoadBalancerManaged, LoadBalancerReady, DNSManaged and DNSReady) to Gateway API resources that created with Openshift Gateway Class and on openshift-ingress namespace.

This proposal was partially generated with the help of Claude/AI

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 21, 2025

@rikatz: This pull request references NE-2183 which is a valid jira issue.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 21, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 21, 2025
@openshift-ci openshift-ci bot requested review from knobunc and rfredette October 21, 2025 18:12
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 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 frobware 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-robot
Copy link

openshift-ci-robot commented Oct 22, 2025

@rikatz: This pull request references NE-2183 which is a valid jira issue.

In response to this:

This enhancement proposal adds the Ingress Controller Conditions (LoadBalancerManaged, LoadBalancerReady, DNSManaged and DNSReady) to Gateway API resources that created with Openshift Gateway Class and on openshift-ingress namespace.

This proposal was partially generated with the help of Claude/AI

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.

@rikatz rikatz changed the title WIP: NE-2183: Initial write on Gateway API conditions NE-2183: Initial write on Gateway API conditions Oct 22, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 22, 2025
@rikatz rikatz changed the title NE-2183: Initial write on Gateway API conditions NE-2183: Openshift conditions on Gateway API status Oct 22, 2025
@Miciah
Copy link
Contributor

Miciah commented Oct 30, 2025

/assign

@candita
Copy link
Contributor

candita commented Oct 30, 2025

/assign

@candita
Copy link
Contributor

candita commented Oct 30, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 30, 2025

@rikatz: The following test 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/markdownlint 31a44a8 link true /test markdownlint

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.

@rikatz
Copy link
Member Author

rikatz commented Oct 31, 2025

the error is valid, it is due to the metadata not containing real approvers and reviewers for now. Once I get some review and approval I can fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

4 participants