OPNET-678: Allow disabling internal DNS#9924
OPNET-678: Allow disabling internal DNS#9924openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
322d1f0 to
ec64c52
Compare
|
This includes #10097 but I split the api bump out because I think it should be easier to review in isolation. |
|
@cybertron: This pull request references OPNET-678 which is a valid jira issue. DetailsIn 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. |
|
/retest |
9d31157 to
dc21cb3
Compare
tthvo
left a comment
There was a problem hiding this comment.
Nice 👍 🚀
I have a couple small questions only :D
Also, I think we need to drop the changes for openshift/api vendor since it's already on main? Maybe, a quick rebase on top of main will naturally solve it...
| { | ||
| FeatureGateName: features.FeatureGateOnPremDNSRecords, | ||
| Condition: v.DNSRecordsType == configv1.DNSRecordsTypeExternal, | ||
| Field: field.NewPath("platform", "vsphere", "DNSRecordsType"), |
There was a problem hiding this comment.
| Field: field.NewPath("platform", "vsphere", "DNSRecordsType"), | |
| Field: field.NewPath("platform", "vsphere", "dnsRecordsType"), |
nit: we should use the serialized name of the field for field path, right? Same questions for openstack, baremetal, and nutanix too 💭
There was a problem hiding this comment.
Yeah, looks like that's consistent with the existing checks. I'll change it.
| APIServerInternalIPs: installConfig.Config.Platform.BareMetal.APIVIPs, | ||
| IngressIPs: installConfig.Config.Platform.BareMetal.IngressVIPs, | ||
| LoadBalancer: installConfig.Config.Platform.BareMetal.LoadBalancer, | ||
| DNSRecordsType: installConfig.Config.Platform.BareMetal.DNSRecordsType, |
There was a problem hiding this comment.
💡 Do we need to set this field in the infrastructure status for platform vsphere, openstack, and nutanix too?
Wire in the internalDNSRecords API field to install-config so we can disable the internal DNS records for deployments using a user-managed loadbalancer. Co-Authored-By: Claude <noreply@anthropic.com>
Also makes the featuregate validations consistent with the existing checks.
dc21cb3 to
534ea54
Compare
|
Also fixed the integration test failure. |
|
/test verify-vendor |
|
/lgtm |
|
/hold cancel |
|
/retest-required The openstack job seems kind of unstable lately, but it did pass on an earlier version of this patch so I don't think it's a legitimate failure. |
|
/retest-required |
|
/retest-required The openstack job failed on different tests this time. Progress, I guess? |
|
/test e2e-openstack-ovn |
|
/hold Revision 534ea54 was retested 3 times: holding |
|
/test e2e-openstack-ovn again? |
|
Hmm, looks like the install couldn't complete... I am not sure what's going on here 😞 |
|
I've reached out to the openstack team to see if they have any ideas. This has passed multiple other on-prem jobs and I can see from some of the job logs that coredns was working correctly in the clusters, so I don't think this patch is causing the failure. |
|
Thanks Ben, I'll leave it to you to remove the hold then :D Hopefully, it is resolved 🤞 |
|
/hold cancel Whenever openstack is done with their fix |
|
@cybertron: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/hold Revision 534ea54 was retested 3 times: holding |
|
/hold cancel |
|
/override ci/prow/e2e-openstack-ovn |
|
@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-openstack-ovn DetailsIn 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. |
No description provided.