Skip to content

feat(chart): add default-nvme-tcp-nr-io-queues setting docs for v1.13.0 and v1.12.2 - #1424

Draft
derekbit with Copilot wants to merge 2 commits into
masterfrom
copilot/feat-chart-update-v1-13-0-v1-12-2-references
Draft

feat(chart): add default-nvme-tcp-nr-io-queues setting docs for v1.13.0 and v1.12.2#1424
derekbit with Copilot wants to merge 2 commits into
masterfrom
copilot/feat-chart-update-v1-13-0-v1-12-2-references

Conversation

Copilot AI commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Documents the new Default NVMe-TCP Number Of IO Queues setting introduced in longhorn/longhorn-manager#5084, which controls the number of I/O queues the kernel NVMe-TCP initiator creates per V2 block-device frontend volume.

Changes

  • v1.13.0 and v1.12.2 references/settings.md
    • Added TOC entry for Default NVMe-TCP Number Of IO Queues
    • Added setting section with default ({"v2":"0"}), valid range (0–128), and description covering fallback semantics, scope (V2 + block device frontend), and effect timing (re)attach

….0 and v1.12.2

longhorn/longhorn#13706

Co-authored-by: derekbit <12527233+derekbit@users.noreply.github.com>
@netlify

netlify Bot commented Aug 15, 2026

Copy link
Copy Markdown

Deploy Preview for longhornio ready!

Name Link
🔨 Latest commit ad6ea16
🔍 Latest deploy log https://app.netlify.com/projects/longhornio/deploys/6a7fe07d69d6af00083ea0b3
😎 Deploy Preview https://deploy-preview-1424--longhornio.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@derekbit

Copy link
Copy Markdown
Member

@copilot How about changing to

The default number of I/O queues the kernel initiator creates when connecting a volume frontend over NVMe-TCP. This caps the per-volume in-flight commands to the number of I/O queues multiplied by the negotiated queue size (128). This setting applies to volumes using the V2 Data Engine with the block device frontend and takes effect on (re)attach. The value can be overridden per volume using volume.spec.nvmeTcpNrIoQueues.

longhorn/longhorn#13706

Co-authored-by: derekbit <12527233+derekbit@users.noreply.github.com>

Copilot AI commented Aug 15, 2026

Copy link
Copy Markdown
Contributor Author

@copilot How about changing to

The default number of I/O queues the kernel initiator creates when connecting a volume frontend over NVMe-TCP. This caps the per-volume in-flight commands to the n...

Done in both v1.13.0 and v1.12.2. Updated in commit feat(chart): update nvme-tcp setting description per review feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants