-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
-
True
-
-
-
OBSDOCS (Oct 2 - Oct 23) #243, OBSDOCS (Oct 23 - Nov 13) #244, OBSDOCS (Nov 13 - Dev 4) #245
-
Moderate
Description of problem:
As per https://github.com/openshift/cluster-logging-operator/pull/1519, spec.collection.logs has been deprecated and replaced with spec.collection. Yet documentation for example in https://docs.openshift.com/container-platform/4.13/logging/config/cluster-logging-collector.html still shows and uses spec.collection.logs which should be fixed to get customers to move to the new API specification.
Version-Release number of selected component (if applicable):
OpenShift Container Platform 4.13 and older
How reproducible:
Always
Steps to Reproduce:
1. Check https://docs.openshift.com/container-platform/4.13/logging/config/cluster-logging-collector.html#cluster-logging-collector-limits_cluster-logging-collector 2. Example shown is using spec.collection.logs
Actual results:
Example showing: spec: collection: logs: fluentd: resources: limits: memory: 736Mi requests: cpu: 100m memory: 736Mi
Expected results:
Example should show spec: collection: fluentd: resources: limits: memory: 736Mi requests: cpu: 100m memory: 736Mi
Additional info:
Eventually more examples, etc. need to be updated but we should avoid examples in general with deprecated API specification
- is caused by
-
LOG-2586 Cannot configure CPU/Memory requests and limits in vector
- Closed
- is related to
-
OBSDOCS-79 Logging: Update CLusterLogging config
- Closed
- links to