Mention KEK requirement in production deployment guide#51
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the production deployment guide to call out the key encryption key (KEK) requirement for multi-instance clusters when using the database secret management provider.
Changes:
- Adds guidance that all instances must share the same KEK to avoid startup failures.
- Points readers to the secret management guide’s key management section for provisioning options (mounted keyset file vs env/config).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: nscuro <nscuro@protonmail.com>
nscuro
force-pushed
the
prod-deploy-guide-kek
branch
from
edfd3ee to
632f039
Compare
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
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.
No description provided.