-
Notifications
You must be signed in to change notification settings - Fork 193
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
[release-4.18] OCPBUGS-44906: AWS: Add Ingress LB IPs to Infra CR when in-cluster DNS is enabled #1168
Conversation
Also set DNSManagementPolicy to Unmanaged when BYO DNS is enabled Implementation for https://issues.redhat.com//browse/CORS-3755
Add tests to verify value of EndpointPublishingStrategy on AWS platform when BYO DNS is enabled.
Add tests for the AWS Platform where the Ingress LB's Hostname is available but the Infra CR needs to be updated with its IP.
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CORS-3755 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
/retitle [release-4.18] OCPBUGS-44906: AWS: Add Ingress LB IPs to Infra CR when in-cluster DNS is enabled |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44906, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-44906, which is invalid:
Comment 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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-44906, which is invalid:
Comment 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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-44906, which is invalid:
Comment 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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-44906, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/close This backport is not required since #1167 made it into 4.18. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44906. The bug has been updated to no longer refer to the pull request using the external bug tracker. 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. |
@sadasu: Closed this PR. 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 kubernetes-sigs/prow repository. |
This is an automated cherry-pick of #1167
/assign sadasu