-
Bug
-
Resolution: Done
-
Major
-
OpenShift 4.14 Async, OpenShift 4.12 Async, OpenShift 4.13 Async, OpenShift 4.15 Async, OpenShift 4.16 Async
-
False
-
-
False
-
-
- There is one indentation fault in Configuring CPU and memory limits for logging components in Documentation:
- Here is the link: Configuring CPU and memory limits for logging components
- Here, `spec.collection` indentation is wrongly mentioned.
apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
name: "instance"
namespace: openshift-logging
spec:
collection: <<== collection indentation is wrongly mentioned
resources:
limits:
memory: 736Mi
requests:
cpu: 200m
memory: 736Mi
type: fluentd
- Due to this `spec.collection` will not get applied in the `ClusterLogging` instance CR.
- The correct configuration should look like the following:
apiVersion: "logging.openshift.io/v1" kind: "ClusterLogging" metadata: name: "instance" namespace: openshift-logging...spec: managementState: "Managed" logStore: type: "elasticsearch" elasticsearch: nodeCount: 3 resources: limits: memory: 16Gi requests: cpu: 200m memory: 16Gi storage: storageClassName: "gp2" size: "200G" redundancyPolicy: "SingleRedundancy" visualization: type: "kibana" kibana: resources: limits: memory: 1Gi requests: cpu: 500m memory: 1Gi proxy: resources: limits: memory: 100Mi requests: cpu: 100m memory: 100Mi replicas: 2 collection: <<== This is the correct indentation format resources: limits: memory: 736Mi requests: cpu: 200m memory: 736Mi type: fluentd
- We need to perform this change in our standard documentation.
- I am going to raise PR for this change and work on PR merge.
- links to
