-
Notifications
You must be signed in to change notification settings - Fork 191
Expose DNS conditions on the ARO Operator #1277
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
Conversation
ef7165b to
9130d46
Compare
b2ea0d2 to
7f93d45
Compare
28a86e5 to
64616dc
Compare
|
Please rebase pull request. |
64616dc to
2d8bdfa
Compare
|
Please rebase pull request. |
jim-minter
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.
Please hold this PR while we work out whether #1296 can get rid of the DNS problem at source.
|
@jim-minter We can close this. If there are any other conditions that are necessary for the operator to add, I can make another branch. |
Which issue this PR addresses:
Fixes 8858773
What this PR does / why we need it:
Places conditions of the DNS servers (custom DNS) on the ARO operator
Test plan for issue:
E2E test will be performed to check all conditions on cluster create. This is being done on PR #1273
Is there any documentation that needs to be updated for this PR?
No documentation. The conditions are appended to the conditions that exist with the operator which include
MachineValid, InternetReachableFromMaster, InternetReachableFromWorkerand nowDNSValid