docs(nvmf-security): remove inaccurate cluster-level security config#167
Merged
Conversation
NVMe-oF security has no cluster-level configuration. DH-HMAC-CHAP parameters are fixed (digests sha256/sha384/sha512, DH group ffdhe2048), applied at the pool level via --dhchap; host access control and per-host keys are managed per volume. Drop the 'two levels / cluster-wide settings' framing and the 'Cluster Level' subsection that claimed parameters are provisioned at cluster creation, and stop listing the full DH-group set as configurable.
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-nvmf-security-no-cluster-level |
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-nvmf-security-no-cluster-level |
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
The NVMe over Fabrics Security concept page claimed NVMe-oF security is configured partly at the cluster level. That is inaccurate — there is no cluster-level security configuration.
Corrections (verified against control-plane code)
cluster createhas no--host-sec(or any security) option; thecluster.dhchapfield is unused. Removed the "two levels / cluster-wide settings" intro framing and the Cluster Level subsection claiming DH-HMAC-CHAP parameters are provisioned at cluster creation.sha256,sha384,sha512; DH group:ffdhe2048(constants.py:DHCHAP_DIGESTS,DHCHAP_DHGROUP). Replaced the list implying all DH groups are selectable.--dhchap) and managed per volume/host.🤖 Generated with Claude Code