-
Notifications
You must be signed in to change notification settings - Fork 199
Remove ingress controller manifest. #715
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
stbenjam
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
|
This isn't working consistently for me locally. It seems the machine-config-operator is not reliably acting on this value at startup. I just had to edit the |
|
bug filed: openshift/machine-config-operator#1024 |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/980/ |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/1032/ |
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1063/ |
|
Ok this looks good now since the latest rebase, @russellb if you're happy we can go ahead and land this? |
This is no longer required, as we install a 3 node cluster by default. The installer will automatically adjust the scheduler configuration to make master nodes schedulable. For more details on that change, see: openshift/installer#2004 Closes issue openshift-metal3#705
1239401 to
93fc294
Compare
|
I've rebased this and updated the commit message to reflect what was remaining. Let's let CI run once more ... |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/1064/ |
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1070/ |
This is no longer required, as we install a 3 node cluster by default.
The installer will automatically adjust the scheduler configuration to
make master nodes schedulable. For more details on that change, see:
openshift/installer#2004
Closes issue #705