Skip to content

OCPBUGS-60492: Gateway service DNS: Add check for nil DNS Public and Private DNS zones#1270

Closed
sadasu wants to merge 1 commit intoopenshift:masterfrom
sadasu:add-check-for-zones-gw-service-dns
Closed

OCPBUGS-60492: Gateway service DNS: Add check for nil DNS Public and Private DNS zones#1270
sadasu wants to merge 1 commit intoopenshift:masterfrom
sadasu:add-check-for-zones-gw-service-dns

Conversation

@sadasu
Copy link
Contributor

@sadasu sadasu commented Aug 18, 2025

Reconcile logic for Gateway Service Controller should check for non-nil Public and Private Zones as per the DNS API specification.

@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 Aug 18, 2025
@openshift-ci openshift-ci bot requested review from alebedev87 and miheer August 18, 2025 17:52
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 18, 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.

Details 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

@sadasu
Copy link
Contributor Author

sadasu commented Aug 18, 2025

@Miciah , @alebedev87 I think this is the better fix over #1269.

The existing unit tests are expected to fail.

@patrickdillon
Copy link
Contributor

@Miciah , @alebedev87 I think this is the better fix over #1269.

+1, from my understanding I think this makes the most sense (handles UPI scenarios & custom DNS), but my understanding of Gateway API and how ingress works in Custom DNS is shaky at best

The existing unit tests are expected to fail.

So they will need to be fixed up, but just waiting for approval on the approach?

Reconcile logic for Gateway Service Controller should check for non-nil
Public and Private Zones as per the DNS API specification.
@sadasu sadasu force-pushed the add-check-for-zones-gw-service-dns branch from 90f03c0 to 784cf4e Compare August 18, 2025 20:00
@sadasu sadasu changed the title WIP: Gateway service DNS: Add check for nil DNS Public and Private DNS zones OCPBUGS-60492: Gateway service DNS: Add check for nil DNS Public and Private DNS zones Aug 18, 2025
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 18, 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 Aug 18, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 18, 2025
@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-60492, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Reconcile logic for Gateway Service Controller should check for non-nil Public and Private Zones as per the DNS API specification.

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 a review from gpei August 18, 2025 20:01
@sadasu
Copy link
Contributor Author

sadasu commented Aug 18, 2025

This fix is preferred over #1269.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2025

@sadasu: 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-operator-techpreview 784cf4e link false /test e2e-aws-operator-techpreview
ci/prow/e2e-azure-ovn 784cf4e link false /test e2e-azure-ovn
ci/prow/e2e-gcp-operator 784cf4e link true /test e2e-gcp-operator
ci/prow/e2e-aws-operator 784cf4e link true /test e2e-aws-operator
ci/prow/hypershift-e2e-aks 784cf4e link true /test hypershift-e2e-aks

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

@sadasu
Copy link
Contributor Author

sadasu commented Aug 19, 2025

This update to the controller is deemed unnecessary.

@sadasu sadasu closed this Aug 19, 2025
@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-60492. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Reconcile logic for Gateway Service Controller should check for non-nil Public and Private Zones as per the DNS API specification.

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.

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

Labels

jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.

3 participants

Comments