Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-37220: Fix DNS for Gateway API on AWS #1108

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

candita
Copy link
Contributor

@candita candita commented Jul 19, 2024

Before this change, a new Gateway API dnsRecord created on AWS was being deleted right after it was published.

pkg/operator/controller/dns/controller.go - make the general watch for dnsRecords skip Gateway API dnsRecords

pkg/operator/controller/gateway-service-dns/controller.go - add a predicate to ensure only dsnRecords for Gateway API are watched; remove the restriction that watched only Services in openshift-ingress namespace; export the ManagedByIstioLabelKey for use by the general dns controller; add logging to ensureDNSRecordsForGateway and deleteStaleDNSRecordsForGateway

pkg/resources/dnsrecord/dns.go - minor tweak and logging added to EnsureDNSRecord
pkg/dns/aws/dns.go - add logging

@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Jul 19, 2024
@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 Jul 19, 2024
Copy link
Contributor

openshift-ci bot commented Jul 19, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 19, 2024
@openshift-ci-robot
Copy link
Contributor

@candita: This pull request references Jira Issue OCPBUGS-37220, which is invalid:

  • expected the bug to target the "4.17.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

Before this change, a new Gateway API dnsRecord created on AWS was being deleted right after it was published.

pkg/operator/controller/dns/controller.go - make the general watch for dnsRecords skip Gateway API dnsRecords

pkg/operator/controller/gateway-service-dns/controller.go - add a predicate to ensure only dsnRecords for Gateway API are watched; remove the restriction that watched only Services in openshift-ingress namespace; export the ManagedByIstioLabelKey for use by the general dns controller; add logging to ensureDNSRecordsForGateway and deleteStaleDNSRecordsForGateway

pkg/resources/dnsrecord/dns.go - minor tweak and logging added to EnsureDNSRecord
pkg/dns/aws/dns.go - add logging

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 19, 2024
Copy link
Contributor

openshift-ci bot commented Jul 19, 2024

[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 ask for approval from candita. 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:

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

@candita candita force-pushed the OCPBUGS-37220-GWAPI-AWS-DNS branch from b04083d to b6dc40b Compare July 19, 2024 19:21
@candita
Copy link
Contributor Author

candita commented Jul 19, 2024

/test all

@candita
Copy link
Contributor Author

candita commented Jul 19, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 19, 2024
@openshift-ci-robot
Copy link
Contributor

@candita: This pull request references Jira Issue OCPBUGS-37220, which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @lihongan

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.

@openshift-ci openshift-ci bot requested a review from lihongan July 19, 2024 19:23
@candita candita force-pushed the OCPBUGS-37220-GWAPI-AWS-DNS branch from b6dc40b to 3101dbc Compare July 20, 2024 00:11
@candita
Copy link
Contributor Author

candita commented Jul 23, 2024

/test all

Copy link
Contributor

openshift-ci bot commented Jul 23, 2024

@candita: 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/e2e-aws-ovn-single-node 3101dbc link false /test e2e-aws-ovn-single-node

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 openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 9, 2024
@openshift-merge-robot
Copy link
Contributor

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.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 7, 2024
@candita
Copy link
Contributor Author

candita commented Nov 25, 2024

/lifecycle-remove stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/severity-moderate Referenced Jira bug's severity is moderate 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants