Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Resource Configuration in yorkie-mongodb Helm chart #872

Merged
merged 2 commits into from
May 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions build/charts/yorkie-mongodb/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,16 @@ mongodb-sharded:
size: *configSize
mountPath: /data/configdb
storageClass: *storageClass
## @param configsvr.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
resources: {}
krapie marked this conversation as resolved.
Show resolved Hide resolved

# Configuration for shard server
shardsvr:
Expand Down Expand Up @@ -154,6 +164,12 @@ mongodb-sharded:
size: *dataSize
mountPath: /data/db
storageClass: *storageClass
## @param shardsvr.dataNode.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
resources:
requests:
memory: 1Gi
limits:
memory: 2Gi

# Configuration for mongos
mongos:
Expand Down Expand Up @@ -196,6 +212,16 @@ mongodb-sharded:
enabled: false
startupProbe:
enabled: false
## @param mongos.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
resources: {}
krapie marked this conversation as resolved.
Show resolved Hide resolved

# Configuration for Prometheus monitoring
metrics:
Expand Down
Loading