To make changes to your cluster logging deployment, create and modify the Cluster Logging Custom Resource (CR).
Instructions for creating or modifying a CR are provided in this documentation as appropriate.
The following is an example of a typical Custom Resource for cluster logging.
Sample Cluster Logging CR
kind: "ClusterLogging"
metadata:
name: "instance" (1)
namespace: "openshift-logging" (2)
spec:
managementState: "Managed" (3)
logStore:
type: "elasticsearch" (4)
retentionPolicy:
application:
maxAge: 1d
infra:
maxAge: 7d
audit:
maxAge: 7d
elasticsearch:
nodeCount: 3
resources:
limits:
memory: 16Gi
requests:
cpu: 500m
memory: 16Gi
storage:
storageClassName: "gp2"
size: "200G"
redundancyPolicy: "SingleRedundancy"
visualization: (5)
type: "kibana"
kibana:
resources:
limits:
memory: 736Mi
requests:
cpu: 100m
memory: 736Mi
replicas: 1
curation: (6)
type: "curator"
curator:
resources:
limits:
memory: 256Mi
requests:
cpu: 100m
memory: 256Mi
schedule: "30 3 * * *"
collection: (7)
logs:
type: "fluentd"
fluentd:
resources:
limits:
memory: 736Mi
requests:
cpu: 100m
memory: 736Mi
| 1 |
The CR name must be instance. |
| 2 |
The CR must be installed to the openshift-logging namespace. |
| 3 |
The Cluster Logging Operator management state. When set to unmanaged the operator is in an unsupported state and will not get updates. |
| 4 |
Settings for the log store, including retention policy, the number of nodes, the resource requests and limits, and the storage class. |
| 5 |
Settings for the visualizer, including the resource requests and limits, and the number of Pod replicas. |
| 6 |
Settings for curation, including the resource requests and limits, and curation schedule. |
| 7 |
Settings for the log collector, including the resource requests and limits. |