-
Notifications
You must be signed in to change notification settings - Fork 417
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
CORS-3713: Extend in-cluster DNS support to AWS Platform #4711
CORS-3713: Extend in-cluster DNS support to AWS Platform #4711
Conversation
In-cluster DNS support was previously added for the GCP platform. Only the platform specific portions of that solution have been updated to include the AWS platform.
@sadasu: This pull request references CORS-3713 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.18.0" version, but no target version was set. 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. |
@yuqi-zhang Could you PTAL? |
/retest-required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logically seems fine, although I don't know how to test this. Is this covered by any existing CI? Alternatively, maybe this should be QE pre-verified?
Will be tested by both QE and CI. This tech preview CI job is being added to test this feature. |
/lgtm As discussed via Slack, looks good because it's basically copy-pasta of the code handling GCP extending the logic for AWS. But if after the feature freeze it turns out we need additional implementation in baremetal-runtimecfg, then we should be reverting this one here. I hope the current code in runtimecfg handles cloud platforms "all-at-once", but we (on-prem networking) never really tested the use of baremetal-runtimecfg in non-metal platforms so there may be gaps. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mkowalski, sadasu, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Yes, code added to baremetal-runtimecfg is generic for cloud platforms and does not need any additional changes to add support for AWS (and later Azure). |
/label acknowledge-critical-fixes-only |
@sadasu: The following test failed, say
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. |
/test e2e-aws-ovn-upgrade |
9a8ee32
into
openshift:master
[ART PR BUILD NOTIFIER] Distgit: ose-machine-config-operator |
In-cluster DNS support was previously added for the GCP platform. Only the platform specific portions of that solution have been updated to include the AWS platform.
- What I did
- How to verify it
- Description for the changelog