docs: document certificate_reload setting in reference config (9.3)#7096
Merged
Conversation
Certificate hot-reload is disabled by default; document the setting so operators know it exists and can opt in. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
macdewee
approved these changes
May 25, 2026
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
3 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.
What is the problem this PR solves?
The
certificate_reloadconfiguration setting was added to these branches (via #7067) but was not documented in the reference config, leaving operators unaware it exists or how to use it.How does this PR solve the problem?
Adds the
certificate_reloadblock tofleet-server.reference.ymlwith accurate defaults:enabled: false(since hot-reload is disabled by default on this branch) andreload_interval: 5s.How to test this PR locally
No code changes; review the reference config diff to confirm the comment accurately reflects the behavior introduced in #7067.
Checklist
Related issues