-
Notifications
You must be signed in to change notification settings - Fork 539
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
inefficient corefile #131
Comments
We have no way of knowing what the pod cidr space is. We cannot determine this programmatically from the k8s api. We can ask the user. But they don't typically know this. Hence the current solution. |
.. with the tradeoff their performance is very bad. Sorry, this is a not a good generic solution. [added] |
This is still true. Probably makes a lot of sense to remove fall through
from kubernetes, as it only there to be abused
…On Wed, 10 Apr 2019, 14:06 chrisohaver, ***@***.***> wrote:
Closed #131 <#131>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#131 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAVkWwEDM_I1ow0g2N9o0dKt6e9XcXerks5vfeHdgaJpZM4bPL4c>
.
|
see duplicate issue and related discussion: coredns/coredns#2723 |
is ineffcient and should be split up into multiple servers.
will kill any reverse look ups.
See coredns/coredns#2593 (comment) for a better one
The text was updated successfully, but these errors were encountered: