-
Notifications
You must be signed in to change notification settings - Fork 1.4k
CORS-4082, CORS-4086: Azure UserProvisionedDNS: Update bootstrap, master and worker ignition files #10058
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
base: main
Are you sure you want to change the base?
Conversation
sadasu
commented
Nov 3, 2025
- Edit bootstrap, master and worker ignition files after they have been created using EditIgnition() which was created as a common method for all platforms supporting this feature
- Provide EditIgnition() with the api and api-int LB IPs for Azure
- Stop creating DNS entries for Azure when userProvisionedDNS is enabled
|
@sadasu: This pull request references CORS-4082 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.21.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. |
|
/jira refresh |
|
@sadasu: This pull request references CORS-4082 which is a valid jira issue. 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: This pull request references CORS-4082 which is a valid jira issue. This pull request references CORS-4086 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.21.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. |
|
/retest-required |
|
/jira-refresh |
tthvo
left a comment
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.
Looks good! I have some code questions 👍
patrickdillon
left a comment
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.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon 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 |
4a331ef to
8fd2272
Compare
tthvo
left a comment
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.
/lgtm
…n files 1. Edit bootstrap, master and worker ignition files after they have been created using EditIgnition() which was created as a common method for all platforms supporting this feature 2. Provide EditIgnition() with the api and api-int LB IPs for Azure 3. Stop creating DNS entries for Azure when userProvisionedDNS is enabled
Copy the CoreDNS pod definifion and Corefile to correct location on bootstrap node during bootkube. That way MCO running on the bootstrap node can start the CoreDNS pod.
8fd2272 to
f485341
Compare
tthvo
left a comment
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.
/lgtm
|
/retest-required |
|
/test e2e-azure-ovn Uh ohh, what's going on... 👀 |
|
@sadasu: The following tests 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. |