Bug 1372457, explained the impact of disabling dnsmasq#2844
Bug 1372457, explained the impact of disabling dnsmasq#2844ahardin-rh merged 1 commit intoopenshift:masterfrom
Conversation
|
@miheer @sferich888 PTAL. Thanks! |
8b7c330 to
86be217
Compare
|
Approved by QE. @miheer @sferich888 PTAL |
|
@rjhowe PTAL |
There was a problem hiding this comment.
@ahardin-rh I think I'm a little confused by the above. Should it say:
"If you want to set up X, then set openshift_use_dnsmasq in the Ansible playbook to false."
or
"If you set up X, then {product-title} sets openshift_use_dnsmasq in the Ansible playbook to false"
?
|
@ahardin-rh Would it be worth suggesting that the entire addition here be included in a Warning box or something? The previous procedure seems to use dnsmasq, so it's a bit jarring seeing this topic as a new section. Otherwise, LGTM! |
e6c4fe5 to
2202b97
Compare
|
@bfallonf Thanks! I think it's a lot of information to place in a warning box, so I made it its own true section. |
There was a problem hiding this comment.
I do not understand this statement, are we talking about the route exposed for the registry or the SKYDNS service name. Even with out dnsmasq we should be able to use both if the cluster is configured correctly. We inject the kubernetes service ip and search domains in the container resolv.conf and take resolv.conf from the host. So we should be able to resolve everything still.
Unless things have changed in later versions.
There was a problem hiding this comment.
@rjhowe Thanks. I removed the statement.
2202b97 to
71c04a1
Compare
|
[rev_history] |
https://bugzilla.redhat.com/show_bug.cgi?id=1372457
and
https://bugzilla.redhat.com/show_bug.cgi?id=1372456