helm: add exporter resource entry to ceph cluster

This adds the new `exporter:` resource key to the Ceph cluster example
yaml. It also set some sane resource requests and limits for it in the
CephCluster section of the rook-ceph Helm chart.

Closes #11914

Signed-off-by: Alexander Trost <galexrt@googlemail.com>
This commit is contained in:
Alexander Trost committed 2023-05-30 17:54:49 +02:00
1 parent 4af3f3784b
commit 178c916012
3 files changed
+10

No files matched your search

@@ -530,6 +530,7 @@ It scrapes for Ceph daemon core dumps and sends them to the Ceph manager crash m
You can read more about the [Ceph Crash module](https://docs.ceph.com/docs/master/mgr/crash/).
* `logcollector`: Set resource requests/limits for the log collector. When enabled, this container runs as side-car to each Ceph daemons.
* `cleanup`: Set resource requests/limits for cleanup job, responsible for wiping cluster's data after uninstall
* `exporter`: Set resource requests/limits for Ceph exporter.
In order to provide the best possible experience running Ceph in containers, Rook internally recommends minimum memory limits if resource limits are passed.
If a user configures a limit or request value that is too low, Rook will still run the pod(s) and print a warning to the operator log.
@@ -540,6 +541,7 @@ If a user configures a limit or request value that is too low, Rook will still r
* `crashcollector`: 60MB
* `mgr-sidecar`: 100MB limit, 40MB requests
* `prepareosd`: no limits (see the note)
* `exporter`: 128MB limit, 50MB requests
!!! note
We recommend not setting memory limits on the OSD prepare job to prevent OSD provisioning failure due to memory constraints.
@@ -331,6 +331,13 @@ cephClusterSpec:
requests:
cpu: "500m"
memory: "100Mi"
exporter:
limits:
cpu: "250m"
memory: "128Mi"
requests:
cpu: "50m"
memory: "50Mi"
# The option to automatically remove OSDs that are out and are safe to destroy.
removeOSDsIfOutAndSafeToRemove: false
+1
View File
@@ -227,6 +227,7 @@ spec:
# crashcollector:
# logcollector:
# cleanup:
# exporter:
# The option to automatically remove OSDs that are out and are safe to destroy.
removeOSDsIfOutAndSafeToRemove: false
priorityClassNames: