Supporting default TLS config for remote clusters#9932
Draft
stuart-wells wants to merge 2 commits intomainfrom
Draft
Supporting default TLS config for remote clusters#9932stuart-wells wants to merge 2 commits intomainfrom
stuart-wells wants to merge 2 commits intomainfrom
Conversation
added 2 commits
April 9, 2026 15:55
Allowing customer configs to include a * section that defines a default rootCaFile for all undefined clusters. Initial Claude changes.
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
1 participant
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.
What changed?
Adding support for a fallback/default TLS section in the client config for remote clusters
Why?
When adding a new server, a user would have to add the new hostname to the config. This change allows for new servers to have a default cert, while still preserving the existing behavior.
Closes #9881
How did you test it?