Defer DNS resolution for TLS server names to improve startup performance#230
Merged
nicklan merged 1 commit intodatabricks:masterfrom Aug 26, 2025
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously it resolved the DNS for every cluster with a
tls_server_nameduring config loading, causingslow startup for kubeconfigs with many clusters.
Instead move DNS resolution to when HTTP clients are actually created, so DNS resolution now only occurs when clusters are actually used.
Testing:
cargo testverified with
cargo runthat startup is << 1 sec