-
Notifications
You must be signed in to change notification settings - Fork 484
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
Is there an option to prefetch for Nodelocal DNS Cache #652
Comments
I would be very nice with a prefetching function, like unbound has, in node-local-dns, so our applications don't notice cache expirys. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The plugin would be included in its entirety, so all plugin configuration options should be available. I am not sure what version of node local DNS you are running, and therefore what version of CoreDNS it is based on. But you could try and make sure vanilla CoreDNS works as you expect? /remove-lifecycle rotten |
My current settings for cache is
If I add the prefetch nothing seems to change.
I cant see prefetched requested in the logs either. I have tested using it using
serve_stale
which works but is not what I am looking for. At the moment I am going off what is in here: https://coredns.io/plugins/cache/. Is there any documentation you can point me to to understand what I can and cant use for Nodelocal DNS Cache?Has anyone else successfully used prefetch with nodelocaldns?
Thanks.
The text was updated successfully, but these errors were encountered: