commit bc5e311e3fa882d1cd4fdc094b6fb50be35b8796 parent 3df719c3d917183be7379589ea63ff729ce7f83f Author: MTRNord <mtrnord1@gmail.com> Date: Sun, 16 Apr 2023 22:18:47 +0200 Do evil stuff Diffstat:
| M | apps/base/rook/release.yaml | | | 62 | ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
1 file changed, 62 insertions(+), 0 deletions(-)
diff --git a/apps/base/rook/release.yaml b/apps/base/rook/release.yaml @@ -96,6 +96,68 @@ spec: - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists + resources: + mgr: + limits: + cpu: "1000m" + memory: "1Gi" + requests: + cpu: "0m" + memory: "512Mi" + mon: + limits: + cpu: "2000m" + memory: "2Gi" + requests: + cpu: "0m" + memory: "1Gi" + osd: + limits: + cpu: "2000m" + memory: "4Gi" + requests: + cpu: "0m" + memory: "4Gi" + prepareosd: + # limits: It is not recommended to set limits on the OSD prepare job + # since it's a one-time burst for memory that must be allowed to + # complete without an OOM kill. Note however that if a k8s + # limitRange guardrail is defined external to Rook, the lack of + # a limit here may result in a sync failure, in which case a + # limit should be added. 1200Mi may suffice for up to 15Ti + # OSDs ; for larger devices 2Gi may be required. + # cf. https://github.com/rook/rook/pull/11103 + requests: + cpu: "0m" + memory: "50Mi" + mgr-sidecar: + limits: + cpu: "500m" + memory: "100Mi" + requests: + cpu: "0m" + memory: "40Mi" + crashcollector: + limits: + cpu: "500m" + memory: "60Mi" + requests: + cpu: "0m" + memory: "60Mi" + logcollector: + limits: + cpu: "500m" + memory: "1Gi" + requests: + cpu: "0m" + memory: "100Mi" + cleanup: + limits: + cpu: "500m" + memory: "1Gi" + requests: + cpu: "0m" + memory: "100Mi" ingress: # -- Enable an ingress for the ceph-dashboard dashboard: