Skip to content

add longhorn/mongodb sc#19

Merged
jcbrtl merged 1 commit into
developfrom
fine-tune-mdb-sc
Mar 3, 2026
Merged

add longhorn/mongodb sc#19
jcbrtl merged 1 commit into
developfrom
fine-tune-mdb-sc

Conversation

@jcbrtl
Copy link
Copy Markdown
Member

@jcbrtl jcbrtl commented Mar 3, 2026

Fine-tuning Longhorn for MongoDB in Kubernetes (MCK) requires a delicate balance... MongoDB has its own application-level replication, running it on top of Longhorn's block-level replication... often leads to general overheads like physical disk writes amplification.

Refs.:

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 3, 2026

CLA assistant check
All committers have signed the CLA.

@jcbrtl jcbrtl marked this pull request as ready for review March 3, 2026 20:31
@jcbrtl jcbrtl merged commit fb4bb1a into develop Mar 3, 2026
1 of 2 checks passed
@jcbrtl jcbrtl deleted the fine-tune-mdb-sc branch March 3, 2026 20:31
description: "The StorageClass name"
prompt: true
default: longhorn
default: longhorn-mongodb
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to default this? Cause this means all that use will use this storage class?

Copy link
Copy Markdown
Member Author

@jcbrtl jcbrtl Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nop. Default changed there so it makes convenient for our packages together to work with defaults mostly (no need to type, just "enter" or --confirm to assume defaults, but you can --set DATABASE_STORAGECLASS_NAME=<sc> if needed) 👍

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.

3 participants