use resty-resolver everywhere #237
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikz
force-pushed
the
one-resolver
branch
5 times, most recently
from
f97b08f to
87070b0
Compare
so it can use resty-resolver instead of nginx one
and try to rely on our resolver exclusively
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #236
depends on 3scale/s2i-openresty#16
This totally removes nginx
resolverdirective and fully relies on our internal DNS resolver.Setting
RESOLVERenv variable still works. Default servers are auto detected from/etc/resolv.confon boot. Works everywhere (native/docker/openshift)./cc @mayorova @mpguerra
/cc @davidor this might be something XC will need on OpenShift to properly resolve redis via a Service.