1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/cluster-logging-cpu-memory.adoc
Satyajeet Munje cc94fd4ee0 OBSDOCS-693
2024-04-24 18:11:38 +00:00

77 lines
1.8 KiB
Plaintext

// Module included in the following assemblies:
//
// * observability/logging/cluster-logging-collector.adoc
:_mod-docs-content-type: PROCEDURE
[id="cluster-logging-memory-limits_{context}"]
= Configuring CPU and memory limits
The {logging} components allow for adjustments to both the CPU and memory limits.
.Procedure
. Edit the `ClusterLogging` custom resource (CR) in the `openshift-logging` project:
+
[source,terminal]
----
$ oc -n openshift-logging edit ClusterLogging instance
----
+
[source,yaml]
----
apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
name: "instance"
namespace: openshift-logging
...
spec:
managementState: "Managed"
logStore:
type: "elasticsearch"
elasticsearch:
nodeCount: 3
resources: <1>
limits:
memory: 16Gi
requests:
cpu: 200m
memory: 16Gi
storage:
storageClassName: "gp2"
size: "200G"
redundancyPolicy: "SingleRedundancy"
visualization:
type: "kibana"
kibana:
resources: <2>
limits:
memory: 1Gi
requests:
cpu: 500m
memory: 1Gi
proxy:
resources: <2>
limits:
memory: 100Mi
requests:
cpu: 100m
memory: 100Mi
replicas: 2
collection:
logs:
type: "fluentd"
fluentd:
resources: <3>
limits:
memory: 736Mi
requests:
cpu: 200m
memory: 736Mi
----
<1> Specify the CPU and memory limits and requests for the log store as needed. For Elasticsearch, you must adjust both the request value and the limit value.
<2> Specify the CPU and memory limits and requests for the log visualizer as needed.
<3> Specify the CPU and memory limits and requests for the log collector as needed.