Backport: [kube-dns] The d8-kube-dns-redirect service has been restored #13510
Conversation
This file contains hidden or 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
Signed-off-by: Paramoshka <parfenov_ivan_42a@mail.ru> Signed-off-by: Andrey Polovov <andrey.polovov@flant.com> Co-authored-by: Andrey Polovov <andrey.polovov@flant.com>
4 tasks
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.
Description
The d8-kube-dns-redirect service has been reverted.
Why do we need it, and what problem does it solve?
The d8-kube-dns-redirect service was used as a forwarding server for node-local-dns. During an upgrade, this service is removed and old instances of local-dns continue to access the non-existent forward server. However, because the service was not responding, and due to the behavior of the cache plugin, specifically the serve_stale 1h verify setting, it waited up to 5 seconds for a response from the forwarding server. This delay can be critical for latency-sensitive applications such as web frontends.
Why do we need it in the patch release (if we do)?
On large clusters, updating node-local-dns pods can take 10-15 minutes, at which point local dns is left without forwarding servers, which can be undesirable.
Checklist
Changelog entries