Skip to content

Conversation

sadasu
Copy link
Contributor

@sadasu sadasu commented Aug 2, 2025

- What I did
Based on enhancement : openshift/enhancements#1468

- How to verify it
Verification still in-progress.

- Description for the changelog

These changes allow MCO to read AzurePlatformStatus containing the API, API-Int and Ingress Load Balancer IPs for Azure platform. These would be used to generate the CoreFile for static CoreDNS pods running on the Bootstrap node and later on control plane nodes.

This feature is behind the featuregate AzureClusterHostedDNSInstall.

@openshift-ci openshift-ci bot requested review from djoshy and pablintino August 2, 2025 17:32
@sadasu sadasu changed the title Extending in-cluster DNS support to Azure CORS-4170: Extending in-cluster DNS support to Azure Aug 2, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 2, 2025

@sadasu: This pull request references CORS-4170 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.20.0" version, but no target version was set.

In response to this:

- What I did

- How to verify it

- Description for the changelog

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 2, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 2, 2025

@sadasu: This pull request references CORS-4170 which is a valid jira issue.

In response to this:

- What I did
Based on enhancement : openshift/enhancements#1468

- How to verify it
Verification still in-progress.

- Description for the changelog

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
Copy link
Contributor

openshift-ci-robot commented Aug 2, 2025

@sadasu: This pull request references CORS-4170 which is a valid jira issue.

In response to this:

- What I did
Based on enhancement : openshift/enhancements#1468

- How to verify it
Verification still in-progress.

- Description for the changelog

These changes allow MCO to read AzurePlatformStatus containing the API, API-Int and Ingress Load Balancer IPs for Azure platform. These would be used to generate the CoreFile for static CoreDNS pods running on the Bootstrap node and later on control plane nodes.

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 sadasu force-pushed the azure-custom-dns branch from b063c1c to deb21a6 Compare August 4, 2025 21:29
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 5, 2025

@sadasu: This pull request references CORS-4170 which is a valid jira issue.

In response to this:

- What I did
Based on enhancement : openshift/enhancements#1468

- How to verify it
Verification still in-progress.

- Description for the changelog

These changes allow MCO to read AzurePlatformStatus containing the API, API-Int and Ingress Load Balancer IPs for Azure platform. These would be used to generate the CoreFile for static CoreDNS pods running on the Bootstrap node and later on control plane nodes.

This feature is behind the featuregate AzureClusterHostedDNSInstall.

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
Copy link
Contributor Author

sadasu commented Aug 5, 2025

/retest-required

3 similar comments
@pablintino
Copy link
Contributor

/retest-required

@sadasu
Copy link
Contributor Author

sadasu commented Aug 6, 2025

/retest-required

@sadasu
Copy link
Contributor Author

sadasu commented Aug 7, 2025

/retest-required

@sadasu
Copy link
Contributor Author

sadasu commented Aug 7, 2025

Unit test failure seems unrelated to the changes introduced by this PR. For example:

TestOSBuildControllerDeletesRunningBuildBeforeStartingANewOne/MachineOSConfig_change: Adding MachineConfigPool "worker" failed: could not sync MachineConfigPools: sync MachineConfigPools failed: could not sync MachineConfigPool "worker": Syncing MachineConfigPool "worker" failed: no current build annotation on MachineOSConfig "worker-os-config"
E0807 16:25:54.027461   45631 wrappedqueue.go:250] "Unhandled Error" err="Adding MachineConfigPool \"worker\" failed: could not sync MachineConfigPools: sync MachineConfigPools failed: could not sync MachineConfigPool \"worker\": Syncing MachineConfigPool \"worker\" failed: no current build annotation on MachineOSConfig \"worker-os-config\"" logger="UnhandledError"

The the CoreDNS pod definition and Corefile for cloud platforms
already exists due to prior work. Supported cloud platforms
is extended to include Azure.
@sadasu
Copy link
Contributor Author

sadasu commented Aug 14, 2025

/test unit

Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logically lgtm based on enhancement. Are there tests/jobs to cover each platform we add?

}
case configv1.AzurePlatformType:
// If DNSType is set to `ClusterHosted`, we expect the Load Balancer IP addresses to be set.
// If absent, that is exoected to be temporary.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: exoected -> expected

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 15, 2025
sadasu added 2 commits August 19, 2025 12:40
Start CoreDNS pod for Azure DNSType is `ClusterHosted`. Building
on work done for GCP and AWS. CoreDNS pod definition and
CoreFile already added as part of support for GCP.
New `update-dns-server` script that adds DNS resolvers to
/etc/NetworkManager/conf.d/dns-servers.conf. The script adds
the host's own IP address and the cloud metadata server's IP
address to the conf file. These would then get added to the
local resolv.conf by NetworkManager.
This script is run as part of azure-update-dns.service
This service runs when the DNSType on the Azure platform
is set to "ClusterHosted".
@sadasu
Copy link
Contributor Author

sadasu commented Aug 25, 2025

/retest-required

@cybertron
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2025
Copy link
Contributor

openshift-ci bot commented Aug 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sadasu
Copy link
Contributor Author

sadasu commented Sep 3, 2025

/tide refresh

@sadasu
Copy link
Contributor Author

sadasu commented Sep 4, 2025

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Sep 4, 2025
@sadasu
Copy link
Contributor Author

sadasu commented Sep 4, 2025

/verified by existing Installer pre-submit jobs.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 4, 2025
@openshift-ci-robot
Copy link
Contributor

@sadasu: This PR has been marked as verified by existing Installer pre-submit jobs..

In response to this:

/verified by existing Installer pre-submit jobs.

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
Copy link
Contributor Author

sadasu commented Sep 4, 2025

/retest-required

@sadasu
Copy link
Contributor Author

sadasu commented Sep 4, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 4, 2025
@sadasu
Copy link
Contributor Author

sadasu commented Sep 8, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 8, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

5 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@sadasu
Copy link
Contributor Author

sadasu commented Sep 9, 2025

/test e2e-hypershift

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0634552 and 2 for PR HEAD 4d7ad60 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 4d7d3d7 and 1 for PR HEAD 4d7ad60 in total

Copy link
Contributor

openshift-ci bot commented Sep 10, 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-serial a10ec10 link false /test e2e-aws-serial
ci/prow/e2e-azure-ovn-upgrade a10ec10 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-mco-disruptive 4d7ad60 link false /test e2e-gcp-mco-disruptive
ci/prow/bootstrap-unit 4d7ad60 link false /test bootstrap-unit
ci/prow/e2e-aws-ovn-windows 4d7ad60 link false /test e2e-aws-ovn-windows
ci/prow/e2e-aws-mco-disruptive 4d7ad60 link false /test e2e-aws-mco-disruptive
ci/prow/e2e-azure-ovn-upgrade-out-of-change 4d7ad60 link false /test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-gcp-op-ocl 4d7ad60 link false /test e2e-gcp-op-ocl

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.

@sadasu
Copy link
Contributor Author

sadasu commented Sep 10, 2025

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit cd9b709 into openshift:main Sep 11, 2025
16 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants